Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
From time to time, members of the Team System team get an opportunity to back away from their corner of the product to go explore another more fully. Team rivalry aside, they are typically impressed by what they find. In this post, Ian Huff of profiling tool fame, takes a closer look at the managed code analysis tool:
For the last two days we had a chance as a team to pick up a pre-release version of Team System and give it a through user scenario test to see if we could sign off on it being a quality product. I actually quite enjoyed this as it gave me a change to try out some of the features that I haven’t had the time to look at before now. For me this mainly meant taking a look at static code analysis and web and load tests. In this blog entry I’ll look a little deeper at the static code analysis tool.
As someone who works on the documentation team, I was happy to read his final thought:
...through the help files I was not only able to fix the issue, but to understand “why” I was fixing the issue.