Visual Studio

I have found this really great VS2010 Extension.

After downloading it, run it and restart your VS2010 environment.

 

This extension spell checks your comments and double quoted strings while you code.

Please note that it doesn’t work with a right click context menu (as in Microsoft Word and other tools) but it gives the caret down with spell checking suggestions.

 

dror 24/11/2010 - 21:06

This Beta 2 should be more stable. The VS team also put a lot of effort (so I hear) on performance improvements.

http://msdn.microsoft.com/en-us/vstudio/default.aspx

 

As always, Scott Guthrie knows how to give us the headlines, best way possible:

http://weblogs.asp.net/scottgu/archive/2009/10/19/vs-2010-and-net-4-0-beta-2.aspx

Itsu Tamam 20/10/2009 - 10:55

 If you get an error message as appears in the post's title, you will probably get a recommendation "try to instal Visual Studio". So don't.

 

I found several techniques that may help solve this problem. Before you try anything (especially messing the registry), try the following command line:

 

devenv /ResetSkipPkgs

 

At least for now my problem is solved.

Itsu Tamam 06/10/2009 - 07:27

Visual Studio 2008 support Java Script IntelliSense. It does so by using a "-vsdoc.js" file, which is saved together with the "original" ".js" file. For example, if you're using JQuery, and use jquery-1.3.2.min.js file, you can put a jquery-1.3.2.min-vsdoc.js file just next to it (available from JQuery download page), and that's it.

 

Unfortunately, this may not work, and all you get is: "Error updating JScript IntelliSense: Object doesn't support this property or method".

 

One of the things may cause this issue is a bug in Visual Studio. If you're using Visual Studio 2008 SP1 (like I do), there's a patch you can install that adds JScript Editor support for “-vsdoc.js” IntelliSense documentation files.

 

Itsu Tamam 08/09/2009 - 04:56

Installing external VS add-ons may be risky - it may break Visual Studio and make it unusable.

 

It happened to me twice: my VS 2008 was broke in a way that I was unable to create new projects, or even new classes. I would think a simple solution is easy to find, but I found myself reading recommendations for hand-fixing the Windows registry.

 

The problem I had was related to TemplateWizardInterface, which was added when I installed the Guidance Automation Extensions (GAX). Installing new add-on re-create the problem. So, here's a real easy solution:

Itsu Tamam 12/08/2009 - 09:07
Syndicate content