In my previous Developing MSBee posts, I mentioned some issues I was having with FxCop and NUnit.

Regarding FxCop, the IDE kept crashing when I tried running fxcopcmd.exe as a post build event. Jeffrey Van Gogh from the FxCop team debugged the problem and discovered it was a MSBuild parsing issue. Specifically, MSBuild attempts to parse the output of fxcopcmd.exe and then add it as regular warnings to the Error List in the IDE. If fxcopcmd can't find a source location for a particular error in the assembly's .pdb, it displays <source location not stored in PDB> as part of the output. This typically happens with violations that are tied to an entire assembly or namespace, as opposed to a particular method. It turns out that using < and > was causing the MSBuild logger to crash, hence bringing down the IDE. Jeffrey has worked around the issue by replacing < and > with [ and ] and this change will be in FxCop 1.35 RTM. Thanks again to Jeffrey for his help in solving this.

Unfortunately, my NUnit problems haven't been solved. As people pointed out, I could use TestDriven.NET along with other tools, although I still feel compelled to find a solution here since it seems like it should be easy. I did determine that the problem is VS; for some reason, the Target macros are referencing the obj directories instead of the bin directories when using External Tools.

Finally, I wanted to share a blog post by Gautam Goenka, a developer on Team Build. The post is a response to a frequently asked question to their team; how to build .NET 1.1 applications using Team Build. In his post, Gautam goes over the simple steps to use MSBee with Team Build.