Fixing Visual Studio 2008 SP1 constant crashing.

While undoubtedly Visual Studio 2008 is a great development tools, it has been reported to be constant crashing and cause the IDE to shutdown unexpectedly and this may causes unsaved work losses.

An description from the MSDN KB state the following:
VS2008 SP1: In Visual Studio 2008 SP1, having windows in non-default locations, for example after docking and undocking windows, when switching between debugging and designing or switching to/from full screen, can result in a crash of the Visual Studio IDE.

This Hotfix was updated on May 11, 2009 to address a shortcoming with the original Hotfix (published Mar 12, 2009) whereby XAML Intellisense may cease functioning after applying the Hotfix. If you have applied the original Hotfix, it is not necessary to uninstall it to apply the updated (V2) Hotfix.


The hotfix for the issue can be downloaded from here : http://code.msdn.microsoft.com/KB960075

Install Windows Automation API 3.0 to make Visual Studio 2010 runs faster.

According to MS Knowledgebase article id 981741, visual studio can run faster if the Windows Automation API 3.0 is installed.

Read more from here http://support.microsoft.com/kb/981741

Setting xUnit as External Tools in Visual Studio

To set xUnit as External Tools in Visual Studio:

1. Go to Tools > External Tools
2. In the screen shown, configure as follow.
3. Command field is pointing to xunit.console.exe (xunit.console.clr4.exe if using xUnit 1.6)
4. Arguments fields does the main trick. You should set it as :
   $(BinDir)$(TargetName)$(TargetExt)

• Check the Use Output window as well to user the Visual Studio Output windows, instead of command prompt.
• You can further drag the xUnit External Tool as a button in your toolbar, or set a shortcut key for it.