PP: Identifying list of unwanted USINGs

[prabhupr]

Hi Folks

In CS project, we use "using" statement to make reference to other
namespaces. For example:
using System;
using System.Data;
using System.Configuration;

At times, there a is a chance that few of them get added by mistake or
must have got added for some need and developers must have forgotten to
remove them back when not required

Question:
1. Is there any easy way (may be some tool) to identify if any of these
namespaces are orphan (not relevant to that CS file) and can be removed
2. What are the dis-advntages of leaving them there as it is. Any
performance issues?

 

[Ray Booysen]

Hi Folks

In CS project, we use "using" statement to make reference to other
namespaces. For example:
using System;
using System.Data;
using System.Configuration;

At times, there a is a chance that few of them get added by mistake or
must have got added for some need and developers must have forgotten to
remove them back when not required

Question:
1. Is there any easy way (may be some tool) to identify if any of these
namespaces are orphan (not relevant to that CS file) and can be removed
2. What are the dis-advntages of leaving them there as it is. Any
performance issues?

I use Resharper. Great tool.

 

[Mark Rae]

I use Resharper. Great tool.

Does the current version support VS.NET 2005?