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?

 

[Michael Nemtsev]

Hello (e-mail address removed),

For looking the unused "using" I recomend ReSharper tool (www.jetbrains.com)

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?

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

 

[Daniel O'Connell [C# MVP]]

2. What are the dis-advntages of leaving them there as it is. Any
performance issues?

No. They are nothing but compiler instructions.