Visual Studio 2010 and .NET Framework 4.0 Details Surface
- By Kathleen Richards
- 09/29/08
Microsoft is revealing more about its plans for the next generation of Visual Studio Team System (code-named Rosario), part of the now officially named Visual Studio 2010 and .NET Framework 4.0 rollout. All of these products are still in the very early stages.
"We've got a name called Visual Studio 2010 and that's about all we've got right now," said Dave Mendlen, director of developer marketing at Microsoft. "We're not saying much more about schedule at this point."
The company is outlining some of the new functionality in Visual Studio Team System 2010, which consists of Team Foundation Server and the Team Suite of role-based Visual Studio clients. This next release will focus on "breaking down the walls between the roles that exist today," said Mendlen. With VSTS 2010, Microsoft is addressing the need to better integrate the functions of the project lead, architect, developers and testers throughout the application lifecycle. Key features in the 2010 Team Suite enable reuse of code assets, modeling across tools and architecture, higher quality test and better collaboration.
SQL Server 2005 Dropped
Going forward, the VSTS Database Edition will be rolled into VSTS Developer Edition.
"Developers are more hybrid today than they were in the past, this need to work not just with the core source code but also with the database is becoming more and more important to them," said Mendlen. "With that in mind, we've made the decision to fold these two products together in the 2010 release of the product."
Starting this month, Software Assurance customers with licenses for VSTS 2008 Developer Edition or VSTS 2008 Database Edition can download the VSTS 2008 Database Edition, VSTS Developer Edition, VS2005 Team System for Software Developers and VS2005 Team System for Database Professionals at no extra cost.
In a surprise move, Microsoft has also decided to discontinue TFS "Rosario" support for SQL Server 2005. VSTS lead Brian Harry explained in his blog: "That was a controversial decision but it is a final decision. The primary driving force behind it is that the Report Server feature in SQL Server 2008 is sooooo much improved over that in previous versions that we simply could not pass up taking advantage of it for Rosario."