October 2012
Intermediate to advanced
384 pages
12h 3m
English
Since Microsoft first introduced what would become Visual Studio Team System (VSTS) back in 2004, .NET development teams have begun improving the way they plan, track, and manage their software development projects. No longer are they tracking code changes in meaningfully-named .zip files or Microsoft Visual SourceSafe, bugs and requirements in Microsoft Excel, and performing automated builds using .bat files. VSTS 2005 (code name Burton) integrated those pillars of software development and even tossed in reporting so everyone could stay informed. The game of software development had changed forever. It had gone professional.
In its first iteration, this stack of tools was marketed as only providing support ...
Read now
Unlock full access