Date: Tue, 20 Jul 2004 09:18:00 +0200
Message-ID: <
[email protected]>
Newsgroups: microsoft.public.dotnet.framework.compactframework
NNTP-Posting-Host: 217.5.221.2
Lines: 1
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.compactframework:57755
X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
#1/2:
For example, if you're using SMTP code, it's pretty easy to figure out
there might be some network related exceptions.
You might not know exactly why it's failing (may be all Cisco routers gone
mad), but you can figure out what to do if something failed.
And yes, you're ultimately responsible for all exceptions (unless there's a
bug in our/3rd party code and exception is thrown in error).
You're getting an exception because you did something and that operation
can not be performed properly.
Example:
- i have a MDA-I with WM2003 installed
- The user opens a connection to the internet
- The user makes something wrong because he selected the WAP connection
instead of the GPRS-connection!
- now the code tries a SMTP.ResolveHost(MyHostName) (something similiar)
- i have a Try-Catch around that!
- BUT: after a timeout the whole application stops with a full-screen .Net
Error message
- WITHOUT the System_SR there is just "Assemblyname of ressource not found"
which implies, that there's something wrong with MY code and the error
(halt!) comes from that
- But WITH the System_SR there comes a very clear error-message that
describes why the system is stopped (havn't got the long text in my mind
but when i read this it was really clear - for the customer too!)
Well... here i DO HAVE a Try-Catch but i'm NOT ABLE to catch this error!
Without System_SR i would never have searched in the connections because i
thought it was my fault (because there is a try-catch i never thought the
application could HALT in any way at THIS point, so i searched all over the
code.... until i installed System_SR and saw what was going wrong!)
And yes, you could do much better than "something bad happened while
resolving a DSN".
see above: in some (many?) cases i can not :'( ...
Now, how would you know which exception to expect? Easy, it's all in the
documentation.
For example, let's take a look at Dns.GetHostByName() documentation: [...]
Aha, here's the list of exceptions you can expect and thus have to process.
Yes, it's not your code and you have no sources, but you know what to
expect from it.
yes - right - but how could i write an exception-handler that handles such
hard HALTs as described above to give the user a better understanding of
what happend?
And why the hell should i code KBs or maybe MBs of own exception-handlers
(and surely will miss some) if it's allready build into the system? That's
really strange
It makes sense to catch errors and give clear messages to the customer
where i except something could go wrong.
But in the else-cases of the catch-clauses i have to display the message of
the exception - at least to write it into a log... but HERE is the point,
that in these cases i simply get NO message withouth System_SR - that makes
searching a error a bit hard because as a developer you cannot always
recreate the error in your own environment - so you need the logs from the
user... but without text? I may know where it happens but not why...
#3.
You're developer; this is why System.SR seems to be good enough to you.
Too bad, it's useless to your customers.
it's not ;-) the texts are really good!
#4
I do see your point. I'm sorry it's not redistributable.
:'( that's really TOO SAD! You are absolutely sure about that?
Do you have a link where this is described?
Boris
)))