Using VS2010 integrated fxcop in continuous integration


In our projects we heavily rely on the Microsoft FxCop engine. FxCop prevents us from making stupid programming mistakes like forgetting to dispose a disposable object etc. For a long time we used the FxCop engine 10.0 which has a command line integration for continuous integration environments. Lately we discovered that the VS2010 integrated FxCop has a much stronger analysis engine and more rule sets which could improve our code base even further. But how do you get the VS2010 integrated...

MsBuild and document include tags => Annoying bug


I was developing a large wrapper library for some classes from System.IO. I wanted to use the original documentation from mscorlib for my wrapper classes because the methods and properties only wrap the underlying components from System.IO. This is easily possible with the document include tag.
But there is a bug in the latest msbuild version which can drive you nuts if you don’t know what to look for.

VS2010 Search + Replace to the rescue


I’m currently working porting a library into another open source project. As I have heavily extended the library my primary goal was to make it work and then compliant to the coding guidelines. A lot of my code contained in the library had automatically generated (with R#) interface implementations which contained blank lines between the curly braces. As you might know this is not StyleCop compliant. Wonderfully I was able to address the issues with the VS2010 Search + Replace dialog and tagged...

Windows7, Resharper 5.1, VS2010 and xunit.contrib problem


Just a short notice. If you are using Resharper 5.1 under Windows7 and xunit.contrib and your unit tests are not executed anymore in VS2010 you need to check the following: Close all running VS2010 instances Upgrade to latest xunit.contrib for Resharper 5.1 If you have xunit.contrib under Program Files\Jetbrains\Resharper\..\Bin\Plugins then move them to [Root]:\Users\[YourUser]\AppData\Roaming\JetBrains\ReSharper\v5.1\vs10.0\Plugins\XunitContrib Open VS2010 again and you should be able to run...

Recent Posts