If you create a class library and add a reference to it from an Azure Web Role or Azure Worker Role you get an error. Here’s how to get around it. The problem is that the class library template for Visual Studio 2010 creates a .csproj file with too few configuration settings. In Visual Studio 2008 the default target platform is AnyCPU. In Visual Studio 2010 it’s x86 and the configuration for AnyCPU is not included. It seems to me this is an error in Visual Studio 2010 Beta 1. This is what a standard .csproj file excerpt...

Tests fail when you reference the wrong version of Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll in Visual Studio 2010. I just tried to run a suite of tests in Visual Studio 2010 that had a reference to the 9.0.0.0 version of Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll. It turned out that the test runner that runs the tests did not want to recognize my version of the ExpectedExceptionAttribute and consequently failed my tests that expect exception. This is a thing to keep an eye out for since it appears to me it is a bug in the current build of Visual Studio 2010. There is no failing run or...

There are different test settings for debugging tests and running code coverage and the like in Visual Studio 2010. When you want to run code coverage you cannot Yesterday I blogged Make sure you edit the same test settings that you use in Visual Studio 2010. I couldn’t figure out why there were two default sets of test settings in Visual Studio 2010; “Local” and “Trace and Test Impact”? Now I know better. After my debacle with the different test settings I promptly deleted the “Trace and Test Impact” settings and kept only the “Local” settings....

I will show below hot to enable Code Coverage in Visual Studio 2010, how to view the results and also how to avoid a strange pitfall that I myself fell into. Just spent the better part of an hour trying to figure out how to get the code coverage results in Visual Studio 2010. Eventually I found out that there was no problem at all. The issue was that I had edited one set of test settings and ran my tests on another set of test settings. Update: I solved this issue and the reason for there being...