Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » VSTS Developing » Code Analysis   (RSS)

Create your own Code Analysis rule set using Visual Studio Team System 2010

In a previous post , I explained how to use Code Analysis in Visual Studio 2010 to detect dead code. In that post, I described the following five Code Analysis rules in detail and how these set of rules form the basis for detecting dead code: Private

Catch string formatting bugs with Visual Studio Team System 2010

Formatting strings is a very common task in .NET development. Examples include formatting dates and currencies, composing a HTML response, creating error messages, etc. One of the downsides of string formatting is that if done incorrectly, you can end

Discover dead code in your application using Code Analysis

Last weekend, I spent a good 30 minutes trying to figure out why I wasn't hitting a breakpoint in a method. Admittedly, I wasn't very familiar with the code since I hadn't written it. It turned out that the method wasn't being called from anywhere, so

Use Code Analysis to measure the quality of sample code

Sample code is great because it allows you to quickly get up to speed with a new technology or learn how an API works and sometimes, you might even use some of the code in your own application. The major downside of reusing sample code is that most often,
 
Page view tracker