OK let me preface this by saying by and large, I’m actually a pretty big fan of Visual Studio Team System. One of the things I don’t like is the breakdown of functionality between the different SKU’s of Team Edition. Case in point…
Our current environment has a separate build server. When we got to the point where we wanted to run unit tests as part of the built process, our QA guy had to install the Tester edition on the build server in order for it to run…that was a few weeks back and now we’re ready to implement static code analysis but he found out he needed the to install the assemblies for that on the same box or would have to install the Developer edition on that build server as well. Now if we had properly planned this little bit out, we could have gotten the unit testing and code analysis covered by installing just the Developer edition in the first place, but my question is why do we need to install these editions anyways? Couldn’t there have been a way to include those assemblies as part of the Team Build installation since that was a separate process/folder on the install media anyway? Then again, maybe we’re going about this all wrong…any tips from those who are out there in the field that have tackled these same problems are welcome J