Every developer’s goal is to write bug-free code that meets their specification. With Visual Studio 2010, there has been a huge focus on testing, and that means it is even easier than usual to write fully tested, stable and secure applications with fewer bugs.

Here I’m going to run down some of the features of Visual Studio 2010 and companion applications that make bug-ridden code a thing of the past.

I recently wrote about how students can make use of Team Foundation Server to improve management of their projects, include version control, and generate reports suitable for their assignments.

You may have also covered various development approaches in your courses at University – and you may have heard approaches like “waterfall”, “agile”, “scrum” and more being batted around – I did and I had no idea what they were on about. After a total of 2 years working in 2 startups (Huddle and TweetMeme) its all starting to make a lot more sense. But without that practical experience, I would have had no idea what these terms meant and what it was like to apply them.

Team Foundation Server is designed to be extensible to support various development profiles. As a result it is a great way to get started actually applying these principles, which will provide all kinds of advantages to you in your projects.

Team Foundation Server is a product that Microsoft have been selling to work with Visual Studio for many years now. Over time it has evolved, and with the upcoming release of Visual Studio 2010, I thought now would be a great time to check out Team Foundation Server in more detail; specifically how it can help students get their projects done faster and better.

Team Foundation Server used to be the companion to Visual Studio Team System (which acted as the client). With VS 2010, Team System has been integrated into the core of Visual Studio. This provides two benefits – better support as it’s baked right in, and more students can get access to it for free!

There are 3 main targets of Team System: