<rant> Yeah, it's a shame, though, that the exception dialog on VS.NET is so brain-dead.
It's losely based on the exceptions dialog in VJ++, but instead of usefully listing the exceptions in a derived-class hierarchy (so you can change the behaviour of an exception, or all exceptions derived from it), it lists the exceptions in a namespace hierarchy - completely useless. </rant> Piers. -----Original Message----- From: A Rafael D Teixeira [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 30, 2002 4:47 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [Mono-list] RFC: Corlib Unit Test on Linux How-To >From: "Linus Upson" <[EMAIL PROTECTED]> >Here is a test case that shows that the .Net runtime looks for a >matching catch block before executing the finally blocks: <SNIP> >I'm not sure why they chose to do this, but it does look intentional. >My only guess so far is that they wanted to allow developers the >opportunity to inspect the program's state with a debugger before any >of the finally blocks ran. > >Linus Indeed, I use that a lot, when debugging in VS.NET. More importantly, in the IDE, you can choose which exceptions (by type/category not by try-block) you want to break into, before it�s processed, either by any catch block or by the finally block. I hope that Mono debugging will integrate that well with SharpDevelop and with Linux Debugging environments. Rafael Teixeira Brazilian Developer _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
