The variable 'MyException' is declared but never used

Question

I need to clear this warning :

try
{
    doSomething()
}
catch (AmbiguousMatchException MyException)
{
    doSomethingElse()
}

The complier is telling me :

The variable 'MyException' is declared but never used

How can I fix this.

Solution 1

1. You can remove it like this:

   try
   {
       doSomething()
   }
   catch (AmbiguousMatchException)
   {
       doSomethingElse()
   }
   

2. Use warning disable like this:

   try
   {
       doSomething()
   }
   #pragma warning disable 0168
   catch (AmbiguousMatchException exception)
   #pragma warning restore 0168
   {
       doSomethingElse()
   }
   

Other familiar warning disable

#pragma warning disable 0168 // variable declared but not used.
#pragma warning disable 0219 // variable assigned but not used.
#pragma warning disable 0414 // private field assigned but not used.

Solution 2

You declare a name for the exception, MyException, but you never do anything with it. Since it's not used, the compiler points it out.

You can simply remove the name.

catch(AmbiguousMatchException)
{
   doSomethingElse();
}

Solution 3

You can simply write:

catch (AmbiguousMatchException)

and omit the exception name if you won't be using it in the catch clause.

Solution 4

You could write the exception out to a log if you've got one running. Might be useful for tracking down any problems.

Log.Write("AmbiguousMatchException: {0}", MyException.Message);

Solution 5

The trouble is, you aren't using your variable MyException anywhere. It gets declared, but isn't used. This isn't a problem... just the compiler giving you a hint in case you intended to use it.

View more solutions

Comments

[Jalal Said]

A list of all compiler errors and warnings are available at the MSDN

[Ram]

The solution given by @fparadis2 is better since not advisable to supress warnings when we can fix it

[Jalal Said]

@dasariramacharanprasad that was my first suggestion, re-read my answer ;)

[Gusdor]

solution #2 is not a solution, it is a mask.

[Jalal Said]

But it is a sharp one isn't it :)

[Eric Hirst]

#2 is useful when you want to look at the exception in the debugger or use it in debug only code. (Yes, I realize that #if DEBUG blocks introduce a code smell of their own.)