Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
I’ve been threatening for 6 months to start blogging about VSTS 2010 features and somehow it’s just never made it to the top of my list. With the Beta 1 release coming increasingly closer, it seems like I’m running out of time to tell you much about it before you can easily discover it all yourself. So now seems like an opportune time to start. Being, overall more intimately familiar with the details of the new TFS features, the series will focus more in that area than others but I thought I’d start with a big picture VSTS overview of what we’re doing in the 2010 release.
As I’ve said in a few posts before it’s a REALLY big release. So to keep this post from being 30 pages, I’m going to keep this list to a very short list of very high level features. The names of them will, in some cases, merely be provocative and I’ll follow up with subsequent posts containing details, screenshots, etc. I’m not going to comment on new VS Pro 2010 features at this point but maybe I will after I get through all the Team System stuff.
There are awesome new features in every area of Team System 2010. However there are 3 really “new” areas that are particularly worthy of note. The most prominent is our investment in tools for testers that help make them amazingly productive, incorporate them into the overall software team and provide for seamless flow of information with the developers. A related new area of investment is what we call “Lab Management”. It is a set of features that makes it very easy for you to deploy and test software in many different configurations and then to debug and fix issues that the testing finds. The other major “new” area is in architecture tools. VSTS 2010 marks a significant departure from 2008 with a plethora of new tools to help you design and understand a wide variety of software systems.
BTW, please don’t ask me when Beta 1 will actually ship. I’m quite certain I’m not allowed to give out dates right now but I’ll just say that the features have been done for a while now and we’re just testing and refining the quality. After that comes the release process. All of this takes a while but sitting on the inside it feels like we’re just about there.
On to the feature list. I’ve put blog links next to each feature area where there is an active blog. Please note this is not a comprehensive list but rather just new features in VSTS 2010. Of course most of the 2008 features will be in 2010 too :)
Architecture (http://blogs.msdn.com/camerons/)
Development & Database (http://blogs.msdn.com/habibh/)
Lab Management (http://blogs.msdn.com/amit_chatterjee, http://blogs.msdn.com/lab_management)
Test (http://blogs.msdn.com/amit_chatterjee, http://blogs.msdn.com/james_whittaker)
TFS (my blog http://blogs.msdn.com/bharry)
If you don’t see your favorite feature here, don’t fret. As I drill into the various areas I’ll give a lot more detail. I’m trying to keep everything pretty high level here and save the detailed feature list for the drill down posts.
Brian
PingBack from http://asp-net-hosting.simplynetdev.com/team-system-2010-overview/
This is a good lists. I wonder VSTS 2010 will be shipped with a 64-bits edition or not!?
Hi,
What about .NET CF projects, can we expect a better integration for testing?
> Improved support for parallel development
DVCS? Offline support?
Brian Harry has create a short list of the high-level features that will be coming in Visual Studio Team
Do you have any estimated date for the RTM?
Good feature list.
What about code review proces? Does this feature will be shiped with RTM or later?
Hassan
If you’re interested in knowing more about the next release of Visual Studio (Pro, Team Editions, and
Around build would there happen to be any addition that would allow us to secure "who" can acuallty queue a build to a given build agent. Would be nice to be able to say only X user can queue a build on this build machine and it's running under Y service account which is the only user that can drop builds on Z network share for seperation of duties compliance.
How do you guys decide which features are "team system" features?
It seems to me some of the items above would be a benefit to *all* developers and should really be in down-level editions.
Thank you for submitting this cool story - Trackback from DotNetShoutout
With the help of the colleagues Bill Maurer, Sam Guckenheimer , Sajee Mathew and Daryush Laqab I have
I've mentioned this before but it seems topical here:
Please make some effort to convince the relevant people that more of these SKUs need to be included in the Microsoft Partner program benefits. As a "certified gold partner with ISV competency" we get all the TFS and Team Dev we can eat (we're not very big) but our product quality (and the degree to which we're locked into MS tools) would improve if we had the other tools as well. Unifying DB and Dev helps but a benefit structure that supported a balance of Architecure, test, and development would be nice.
As it is, the champions of process improvement lose to the champions of cash conservation pretty much every game :-(
I realize that there are other customer profiles besides ISVs and there are other sides to the business case. I'm just taking advantage of this venue to advocate a change that would benefit me.
Thanks,
-swn
While the various Visual Studio teams are working on our first beta release, I thought I’d point out
@Tzu-Yie,
Yes, TFS 2010 will be supported on 64-bit for all tiers (including the AT).