Beta 1 - And Still No Team System?
I just installed VS.NET 2005 (well, that’s not true. I installed it the day that it went up on MSDN). If you know me, you know that I’m excited about Team System – or at least from what I have read about it. You see, I haven’t actually seen Team System in action yet – except for the walkthroughs published on the Team System site and of course the “end to end” demo (end to end as long as you are a developer who focuses on Developer tools. In my crazy mixed up world software begins and ends with requirements – so, I’m slightly bummed that the “analysis” workflow isn’t really represented in much of what I read about Team System).
Please don’t get me wrong – I’m excited. Team System is going to be good- probably GREAT compared to what I’m used to using at most client sites (um… that would be NOTHING folks except maybe the free tools or home grown Sharepoint solutions).. But I’m worried. I’ve been involved with the Whidbey – oops – Visual Studio 2005 program for a while now… and I’ve gotten to “touch” many of the features in this new development environment – but I haven’t really gotten to touch all of Team System. Sure there are the basic testing tools… but I want to apply all of Team System across all supported roles (I would prefer to say workflows there) on scenarios I know have caused me problems in the past. But I can’t… My personal concern is that Team System won’t receive the same level of public scrutiny that the remainder of the features in VS 2005 has received. I know Team System is a framework – I know it’s extensible – I’ve read it all… but I haven’t used the full product yet on any “real” project. I’m really hoping that day will come very soon – and hopefully before Beta 2 because I fear that by that time it will be much too late to present any constructive feedback.