hamang.net

re-sign assemblies for code coverage in test configuration

I'm still trying to understand the testconfigurations in Visual Studio 2005. Having a rather standard setup of a webproject by having the presentation in a ASP.NET Web project and the business components in a Library project as well as some other utility projects. We are running code analysis on the projects to follow the guidelines of coding standards set by FxCop.

The utility assemblies and the business component are all strongly typed as suggested by the code analysis. I have configured a test project (using the default created localtestrun.testrunconfig) and specified to run certain tests for the different assemblies. Now here comes the problem. In the localtestrun.testrunconfig the code coverage should also be analyzed. This works fine by re-signing the strongly named assemblies, but in the GUI for the test configuration, it is only possible to specify one key file to use for re-signing the assemblies (or actually only one assembly). What were they thinking? Should I use one key file for all my assemblies? I don't think so.

The solution is: Open the localtestrun.testrunconfig in an xml editor (notepad, XmlSpy, whatever) and you will se that each Assembly has a node for specifying the keyFile. so, Microsoft actually supports the feature by re-signing each assembly (which is logical), but the testconfiguration GUI in Visual Studio does not! Please give me a service pack to VS (pronounced Vicous Studio) 2005 soon, I still consider it a BETA product.

No comments yet.

Leave a comment