I've been remiss in blogging lately so let me update you on MSBee's progress. We're heading into the third week of Sprint 3 and we're still on course for RTM in early May. With our ResolveComReference work complete, we're focused on preparing for the shared source release.

One issue I've been working through is transitioning to the publicly available version of FxCop. MSBee is developed using Visual Studio Team Suite, which includes a special version of FxCop that is integrated with MSBuild via a task and is controlable via the VS IDE. For the shared source release, I want users to be able to build MSBee without needing any version of Visual Studio. Additionally, I want to maintain our FxCop builds so defects in code contributions can be caught. To accomplish this, I'm working on switching MSBee from FxCop in VS 2005 Team Suite to FxCop 1.35, which is available on GotDotNet.

The problem I'm having is with VS crashing. I've set up a post build event that runs FxCopCmd.exe. When FxCop finds no violations, the build succeeds with no issues. When a violation is discovered, it's written in the Build Output window. Unfortunately, Visual Studio crashes immediately afterwards due to an ObjectDisposedException. One possibility is that there's a conflict between the two versions of FxCop on the machine, although I'm skeptical of that being the culprit. Another cause may be related to VS trying to parse the FxCop warning that gets written to the console. Or it could be something completely different. If you've experienced this problem before or know of other possible causes, feel free to leave a comment.