Wow, last week was a whirlwind! Dave Mendlen and myself spent a lot of time with our friends in the press on both coasts, and everywhere in between, talking about the next release of Visual Studio and Visual Studio Team System, now officially called "Visual Studio 2010" and "Visual Studio Team System 2010". To see the general gist of what was discussed, check out this page on MSDN, and a Team System specific one here. But again, those links just give you the high level. I’d like to point out a few more details and resources that can round out your understanding of what we are doing around here.
Brian Harry, as usual, has a great post that dips a little more into the business aspects of what 2010 is all about. Check that out.
Gert Drapers has already spent a little time talking about the fact that in 2010, we will be merging the Database Edition and Developer Edition SKUs into one box. He titles the post as "Team Developer + Team Data = Team Developer", but I think it would have been better to title that one "Team Developer + Team Data = One Great Product!".
A lot of discussion has occurred around the modeling capabilities in 2010, specifically around what the next version of Architecture Edition will contain. I wanted to point out a few Channel9 videos that goes into a bit more detail, showing bits that will be in our next CTP. I did more of an overview discussion of what the product is all about, how we are actually supporting two major scenarios in the product ( what we are referring to as "Top Down" and "Bottom Up" modeling ). See that video here. That video tees up two follow on videos which have also been posted today by Suhail Dutta and Mark Groves, Program Managers on my team.
Suhail discusses the "Bottom Up" features of our tooling. Check it out here. Suhail does a great job talking about how to product can quickly view diagrams grouped by namespace, showing dependencies between those namespaces, and how the Architecture Explorer can be used to further refine the information being displayed. He shows how easy it is to create a Sequence Diagram from existing source, simply by right clicking in the VS code editor and selecting "Generate Sequence Diagram…"! He also describes some additional refinements to the Layer Diagram and how easy it will be to incorporate Architectural Validation ( a very hot topic as we spoke with the press! ) into your MSBuild processes.
Mark takes on the "Top Down" feature of the tool, which is really hiliting the five UML diagrams that will be shipping in the box in VSTS 2010. He also gives you the first peak at our Model Explorer ( a logical view of the entire modeling store ), as well as points out the addition of a new Modeling project that will house the UML data. Check this video out here.