Compiler warning for unused alias?

Question

Hi,

I regularly use aliases when using deeply nested enumerations such as:
using e7 = MY_NAMESPACE.CAllEnumerations.ENUMERATION7;

and then instead of having to type:
int ThisValue = MY_NAMESPACE.CAllEnumerations.ENUMERATION7.FIELD3;

I can type:
int ThisValue = e7.FIELD3;    // Sweet...

My question is whether there is any way for the compiler to warn me of unused aliases? For example, if I add an alias for ENUMERATION6 and ENUMERATION7, but then delete references to ENUMERATION6, can the compiler find the line:
using e6 = MY_NAMESPACE.CAllEnumerations.ENUMERATION6;

and warn me about it? Using VS2005.
Thanks,
Alain

Answer 1

Why dont see show us whole code?

It seems that ENUMERATION6 AND 7 are integer fields (or propperties), but I dont know what you wanna ask it!?

If there field (or property) exists, compiler will say notihng, else it will.

---

Mitja

Answer 2

If you mean can you delete the using statements, such as in.....

using MY_NAMESPACE.CAllEnumerations.ENUMERATION7.FIELD3;

using e7 = MY_NAMESPACE.CAllEnumerations.ENUMERATION7;

....and deleting the first line, then compile it and see what happens.  Because the second line used the fully namespace name, then the compiler should be able to resolve the type in the referenced assembly. Also, the "using e7" line above has a scope limited to the file in which it appears.  This is true, as you may not have noticed, for all using statements that appear at the top of code files.

Rudy   =8^D

---

Mark the best replies as answers. "Fooling computers since 1971."

http://thesharpercoder.blogspot.com/

Answer 3

The compiler will not warn you about unused, existing aliases.  There are many third party tools that will handle this, however.  For example, Resharper includes an option that will remove all unused aliases in a file.  I believe a similar option is available in CodeRush and other similar code-assist products.

---

Reed Copsey, Jr. - http://reedcopsey.com
If a post answers your question, please click "Mark As Answer" on that post and "Mark as Helpful".

Answer 4

Well, I have only VS2010 at hand. Here we have Organize Usings > Remove and Sort in the code editor, which does that for us..

Answer 5

Well, I have only VS2010 at hand. Here we have Organize Usings > Remove and Sort in the code editor, which does that for us..

Remove Unused Usings is new in 2010 (http://msdn.microsoft.com/en-us/library/bb514114(v=vs.100).aspx).

---

Reed Copsey, Jr. - http://reedcopsey.com
If a post answers your question, please click "Mark As Answer" on that post and "Mark as Helpful".

Answer 6

Thanks for the response, Reed. I'll have a look at Resharper.

Regards,
Alain

<Reed Copsey>; <Jr [MVP]> wrote in message news:[e-mail]...

Well, I have only VS2010 at hand. Here we have Organize Usings > Remove and Sort in the code editor, which does that for us..

Remove Unused Usings is new in 2010 (http://msdn.microsoft.com/en-us/library/bb514114(v=vs.100).aspx).

---

Reed Copsey, Jr. - http://reedcopsey.com <http://reedcopsey.com>
If a post answers your question, please click "*Mark As Answer*" on that post and "*Mark as Helpful*".

Answer 7

It already existed in Visual Studio 2008.

Looks like that's when it was added:

http://blogs.msdn.com/b/djpark/archive/2008/08/16/organize-usings-across-your-entire-solution.aspx

"One of the features I worked on for the Visual Studio 2008 release was the new "Organize Usings" feature."