- Recent
- Popular
- Tags (0)
- Subscribers (4)
- Spell checker update 2.2: full support for VS 2008 SP1, simpler setup and a few bug fixesNovember 28
-
Download: VSSpellChecker.msi
What's new in version 2.2:
- Spell checker now fully supports VS 2008 SP1
- Content of <code>, <abbr> and <address> elements is ignored
- Setup no longer requires COM registration, it uses VS AddIn registration in XML file
- List of words to ignore (SpellChecker.ignore file) was moved from AppData to AddIns folder
- Fixed bugs:
- Add To Dictionary may corrupt Word custom dictionary file dictionary file was not in Unicode
- Windows update to MSXML may cause "Ignore" and "Add To Dictionary" command to disappear
- After word was added to dictionary it may continue to be flagged as an error until VS is restarted
Note: There is no v2.2 for VS 2005 or VS 2008 RTM. From now on updates will be provided for VS 2008 SP1 only. Version 2.1 will remain available for VS 2008 RTM and VS 2005 SP1.Spell checker supports text verification in:
- HTML style comments <-- HTML -->
- ASP.NET server side comments: <%-- ASP.NET --%>
- JScript, C# and C++ comments: // C++ style comments
- Where to get the Localized Languages of Silverlight 2 ToolsNovember 26
-
I am proud to announce we have released Silverlight 2 Tools localized in 8 languages! Please follow the links below to get the language of your choice.
Download page details: Chinese (CHS)
Download page details: Chinese (CHT)
Download page details: Spanish (Traditional Sort)
Download page details:
- Web Platform InstallerNovember 25
-
Yesterday Microsoft released Web Platform Installer (WPI) Release Candidate to the web at http://www.microsoft.com/web/channel/products/WebPlatformInstaller.aspx. Betas have been available for a while, but the release version contains several new features. This is a one-stop-shopping installer for free Microsoft web development software; everything you need in one place.
The web page contains everything you need, including a video walkthrough. Here’s an overview of what you’ll find:
On the web page, just click “install now” to get started. You can run the installer directly from this link; there’s no need to save it to disk. The installer itself is light-weight and its payload is always downloaded separately.
- Workaround for a slow closing of Web projectsNovember 21
-
A few users reported that with Web projects located on a remote machine closing project or solution may hang Visual Studio and Visual Web Developer Express for several minutes. We fould that the issue may be caused by VS logging component that collects information on product usage. This is an opt-in feature activated in Help | Customer Feedback Options... The feature may cause logger to walk through folders on a remote server calculating project complexity. The feature does NOT send your project to Microsoft, it just collects some statistics on the project. If you are experiencing slow project close, try switching off participation in the feedback program in Help | Customer Feedback Options... dialog. If it does not help, try disabling component in registry by changing
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Packages\{2DC9DAA9-7F2D-11d2-9BFC-00C04F9901D1}
to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Packages\Disabled-{2DC9DAA9-7F2D-11d2-9BFC-00C04F9901D1}
Thanks
- JScript IntelliSense FAQNovember 18
-
I've been reading through the 70 or so comments on our last 2 jQuery posts. There have been a lot of great questions. Apologies for not being able to answer them sooner (I was busy preparing for Dev Connections). Instead of answering them inline with the comments, I'll try to paraphrase the popular issues here and answer them centrally.
1. I have a ton of Content Pages, do I need to put script references for IntelliSense in each one?
No, you do not need to repeat the script references on each content page. Visual Studio 2008 will auto-detect the presence of a master page and scan for references in that file. Thus, placing references in the master page is all you need to do.
2. I put a vsdoc reference in the Master Page, why is IntelliSense not working in a User Control?
User Controls do not specify a master page. Thus, there is no way for Visual Studio to guess which master page the user control will end up on. Generally, we simply can't predict which file a user control will end up on. Thus, we are unable to provide IntelliSense.
"Shail" provided the best suggestion, which is just to include a list of script references you want on your user control, then wrap those controls with a "<% if (false) ... %>" to make sure you don't redundantly include scripts at runtime.
I can see a centralized list of references helping this scenario, which leads into the next question...
3. Is there a way to specify
