The first week of the first MSBee sprint has been very fruitful. The MSBee code and its unit tests are just about FxCop clean. Additionally, I've had time to investigate different infrastructures for our scenario tests. Some things I've learned over the past week are:

TFS shelveset comments are limited to 2,048 characters. I discovered this when adding information about the FxCop changes I've made, and background information on particular MSBee files, into a TFS shelveset for the code reviewers.

FxCop warnings are not treated as errors when setting the TreatWarningsAsErrors property on the MSBuild command line. This was discovered since we use a check-in system (named SNAP) to submit new or changed code to our depot. With this system, I can both build and test MSBee before checking in code; if the build breaks or a test fails, the check-in is rejected. Consequently, I was hoping to enable code analysis for MSBee and catch FxCop warnings as errors so the build would fail if I attempted to check-in code that wasn't FxCop clean. I suspect there is a way to do this from the command line but I haven't really looked into it yet.

There's no way to group edit TFS Work Items within the VS IDE. We're using TFS to store our SCRUM sprint backlog items as work items. After loading all the data in, we discovered a couple places where we needed to change a field in several work items. I assumed you could select multiple work items, right click, and there would be some menu item like "Group Edit Work Items". From what I've seen thus far, this can't be done in the IDE. However, you can quickly edit multiple work items by exporting your work items into Excel and then making the changes.

Speaking of TFS, I mentioned a few posts ago that a fellow Aftermarket Solutions developer was working on a TFS administration tool. He now has his blog up at: http://blogs.msdn.com/kannans/ so I encourage you to check it out.

Also, our Aftermarket Solutions PM's have created a MSDN forum for the Aftermarket Solutions team. The forum is at: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=291&SiteID=1. Feel free to post questions or comments and share with us tool ideas you'd like to see developed.