[2005] Immediate Window - a lot of first chance exceptions!!!

Hi, I have no errors in my program, or warnings, or anything, it runs great.

But I see in the immediate window when my program is running a lot of errors, and I am wondering what they mean?

Code:

---

A first chance exception of type 'System.ArgumentOutOfRangeException' occurred in System.dll
A first chance exception of type 'System.IO.DirectoryNotFoundException' occurred in mscorlib.dll
A first chance exception of type 'System.ArgumentOutOfRangeException' occurred in System.dll
A first chance exception of type 'System.ArgumentOutOfRangeException' occurred in System.dll
A first chance exception of type 'System.Security.Cryptography.CryptographicException' occurred in mscorlib.dll
A first chance exception of type 'System.Security.Cryptography.CryptographicException' occurred in mscorlib.dll
A first chance exception of type 'System.Security.Cryptography.CryptographicException' occurred in mscorlib.dll
A first chance exception of type 'System.Security.Cryptography.CryptographicException' occurred in mscorlib.dll
A first chance exception of type 'System.Security.Cryptography.CryptographicException' occurred in mscorlib.dll
A first chance exception of type 'System.Security.Cryptography.CryptographicException' occurred in mscorlib.dll
A first chance exception of type 'System.Security.Cryptography.CryptographicException' occurred in mscorlib.dll

---

What do they mean?

Thanks

There are some good explanations on this forum, just search for "first chance exception".
You have a setting in VS set to show First Chance Exceptions. If you don't want to view them, find the setting and change it.

http://blogs.msdn.com/davidklinems/a...12/438061.aspx

http://support.microsoft.com/kb/105675

http://forums.microsoft.com/MSDN/Sho...42215&SiteID=1

Are they bad, is what I am wanting to know?

A first chance exception message is merely telling you that an exception has been thrown. Exceptions should be avoided if reasonably possible but they are a part of programming. If your app doesn't crash then it means that all those exceptions are being handled. If they're being handled by your code then you should examine that code to see whether it's reasonable that they are all being thrown in the first place. If they're being handled by system code then you've got no control over it.

Of course, you could almost certainly have got that information by following the links provided. " Ask first, look for yourself later" is not the best MO for a software developer.