Re: Problems Handling Errors Correctly

Peter,

Seriously though, your past experience is not necessarily going to help you with things you are unfamiliar with. I've been programming a fair bit longer than you have, but I'm still practically a newbie when it comes to .NET and C#. Practically every day I run across something that my past experience hasn't helped me at all with.

Ah, well you are an old timer then. <g>

Seriously, I have spent a lot of time looking at .NET documentation. In many respects, I find it severely lacking where many methods or properties have a tiny description that provides no more information than simply looking at the name of the member. But, yes, there are ways to find certain things if you figure out where they are. And I'll contunue to examine the online help, but I'm still not happy with much of it and think much could've been done better.

So, no matter how experienced you are, it is often helpful to keep in mind that there are always new things to learn. It's human nature to blame the docs or the framework or whatever, but usually if you can just try to put yourself in the same mindset as the human being who designed the docs or the framework or whatever, things that seem arbitrary and a "pain in the ass" turn out to just be a part of an unfamiliar-but-consistent design.

As I mentioned, I had the opportunity to have conversations with several of the .NET developers when it first came out. I have some idea where they are coming from. Personally, I think some of the issues with the .NET documentation is simply due to the depth of the product and the priority, or lack thereof, of being more thorough.

BTW, one thing I do recall saying to the developers was that the docs should clearly indicate to me whether or not a particular method (or property) can possibly raise an exception. At the time, they agreed but I'm also having trouble seeing any indication of that. Do you happen to know the "magic incantation" to obtain that information?

Thanks.

Jonathan

.

Loading