or is this yet another case of a half-baked Microsoft solution? These are called Checked Exceptions and the aren't included in C# for some very good reasons. There's some academic debate as to whether they actually provide benefit. There are some fairly learned people who say that, in large projects, they actually are a detriment and do not carry their own weight in productivity. -c

I'm still fairly new to C#, after having been assigned to a short development project using the Microsoft platform.  I usually code in Java, and I find the lack of a 'throws' clause in C# very dull.  It is very preferable to have a compiler do all of the hard work of ensuring that all exceptions are caught.  Is there any way that this can be accomplished in C# or is this yet another case of a half-baked Microsoft solution? Thanks, James

their own weight in productivity. Could you cite the references? Thanks. There was a discussion on this last week. Do some google searching and some groups.google.com searching and you'll find some of those discussions. Basically, it boils down to the fact that large projects get bogged down with checked exceptions, and you either deal with all the menutiae, or you end up just throws Exception on every method (which is what usually happens) at which point you've lost the whole point of checked exceptions. For a small project, it's nice, but it just doesn't pan out in large projects. In fact, there has been some discussion about removing them from Java (you should find this in your google searches). -c

These are called Checked Exceptions and the aren't included in C# for some very good reasons. There's some academic debate as to whether they actually provide benefit. There are some fairly learned people who say that, in large projects, they actually are a detriment and do not carry their own weight in productivity. Could you cite the references? Thanks.

You might want to make some attempt to lookup the answer before critizing the language and Microsoft. C# includes a full robust exception handling system involving the following keywords: <snip You might want to read the question carefully before criticising the original poster He's not asking for exceptions, he's asking for *checked* exceptions. Unlike Chad, I find that checked exceptions work very well even in large projects. There can be times when you need to have a general exception (although I never use bare Exception for it myself, as that covers things that you *don't* want to bubble up unnoticed) but it still helps with all the *other* exceptions. Like James, I miss checked exceptions in C#.