Writing Maintainable and Robust Applications using Visual Studio Team System – Free Webinar


My good friend Randy Pagels will be presenting a fantastic live webinar for anyone looking for more information on the Developer Edition of Visual Studio, or for anyone who already has it but wants to learn how to use it more effectively. 

Event Overview

The impact of software defects is one of the reasons it is difficult to control the costs of the development and deployment activities on software projects. It is commonly accepted that defects that get resolved later in the development cycle cost more to fix. Learn how you can reduce defects by using the tools provided in Visual Studio Team System Developer Edition.

Duration: 75 Minutes

Start Date: Tuesday, June 02, 2009 1:30 PM Central Time (US & Canada)

Event ID: 1032416678

 

Topics Covered

  • Why did we build Visual Studio Team System?
  • What is Visual Studio Team System (VSTS) & Team Foundation Server?
  • Code Analysis - Code Analysis runs rules over your code to help find potential bugs, security concerns, performance gains, and more.
  • Code Metrics - Code Metrics is a new tool that not only allows you to get an overall view of the health and quality of a project, but also allows you to identify and weed out those complex and un-maintainable hotspots.
  • Code Profiling - The Profiler analyses your application as it runs to find critical resources, such as CPU use, memory use, or disk use.  It commonly is used to find the slow segments or memory hogs of an application.
  • Unit Testing with Code Coverage - Unit testing is the technique of writing code to exercise and test small units of your application, usually at the method level. Code Coverage is a feature you get with Team System that indicates how many lines of code have been touched, or not exercised, by your tests.
  • Code Profiling w/ Unit Tests - We've seen the profiler address performance issues. The unit testing enabling you to exercise specific methods. Now let's combine the tools to drive the scenario you're collection performance data on.  By using the profiler on a unit test we can easily limit the scope of the profiler to collect targeted data.

 


Skip to main content