Developers moving into VS 2005 say foundation for collaboration is poured, but features still ... UNDER CONSTRUCTION



Email    print   
November 15, 2006 —  (Page 1 of 5)
Microsoft’s Visual Studio development platform has been a cornerstone of the company’s development strategy for years. Essentially, if one intends to develop for .NET, the Visual Studio IDE is the only reasonable choice of tool. Although the community seems to be satisfied with the core of the ecosystem—the core IDE, languages and so forth—some discontent with the way Microsoft has handled the challenges of a rapidly shifting landscape lies just below the surface.

With Windows Vista due to land in the hands of business customers at any moment and general availability due at the end of January, there’s a growing sense that Microsoft may unintentionally be offering its customers an excuse to avoid the new operating system. The disconnected release of the APIs in Vista, and the tools to fully exploit them—not due until the release sometime next year, maybe, of Visual Studio “Orcas”—provides another reason for businesses to do so, beyond Vista’s hardware demands.

But perhaps of most concern to enterprise developers is a sense that the key collaboration tools Microsoft offers to developers—the Visual Studio Team Foundation Server and the associated role-based packages aimed at architects, testers and, soon, database professionals—are a long way from being complete.

A CUSTOMER LOOKS AT TFS
In conversations with members of the Visual Studio community, there appeared to be a great deal of agreement that Visual Studio’s Team Foundation Server (TFS) has a way to go before it’s as mature as the rest of Visual Studio. Although several people echoed these sentiments during interviews, one was particularly eloquent on the pros as well as the cons of TFS.

Chris Kinsman, founder of custom development organization Vergent Software, described the experiences of his developers as being typical of “a 1.0 release, with all that implies and intends.” Vergent’s development teams started using TFS because source code control was an issue for them and the mix of CVS and VSS (Visual Source Safe) wasn’t getting the job done.




Pages 1 2 3 4 5 


Share this link: http://sdt.bz/29789
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Team Foundation Service gets first major update
Improved Web experience and performance highlight the first update to the Microsoft service announced in mid-September Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb