How are you creating a file on the client from an ASP.Net application? The
user will have to go through a "file download" browser dialog for each such
file (to prevent a malicious app from downloading something evil to the
machine); unless the purpose of the app is to produce such files, and yo
> If Mark would like another revision, I would suggest that we could make the
> point even clearer by stating that:
I've integrated your comments, thanks for the input! I also added some
links for the more "controversial" points.
--
"Under capitalism, man exploits man. Under communism, it's just
I'm not going to take this pointless discussion any further - I was
merely pointing out that there are some perfectly legitimate use cases
for catching System.Exception - you are of course entitled to your own
opinion
Andrew
-Original Message-
From: Unmoderated discussion of advanced .NE
CreateNew: Your "hypothetical" application didn't mention any
requirements; so, I assumed it might use any of the available options.
Your comment suggested you can simply catch an Exception class and
MessageBox.Show(ex.Message) whenever you use File.Open(). My response was
there are situations, so
See below..
-Original Message-
From: Unmoderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Peter Ritchie
Sent: Monday, September 19, 2005 11:10 AM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: [Spam:* SpamScore] Re: [ADVANCED-DOTNET] Best way to hand
Off the top of my head:
* 'The file "filename" already exists.' is sufficient for your users when
you try use FileMode.CreateNew? I would want to ask the user if they wish
to overwrite so they don't have to open Windows Explorer and delete the
file.
* 'Access to path "filename" is denied' is suffi
You put up a MessageBox showing ex.Message - in response to the user
typing in a filename that you can't open
In fact this is a good case in point where you will be more robust to
the CLR adding a new exception, not less
Andrew
-Original Message-
From: Unmoderated discussion of advanced
How can you "handle" the exception if you don't know what type it is?
What happens if the next version of the CLR adds another exception type
that is thrown by that function; how can you possibly deal with that
exception properly?
It's always easier to write less robust code; but, that doesn't mea
There is some argument for a few exceptions (:)) - for instance
File.Open throws a variety of exceptions, not all of which derive from
IOException - its much easier to just catch System.Exception in this
case
Andrew
-Original Message-
From: Unmoderated discussion of advanced .NET topics.
Dear Frinds,
In the context of handling errors, I wud like to take our discussion a bit
ahead.
I would like to know the following things:
1. What information we should store in the log files.
2. I am having a XML file created at the client side. The
application is based on ASP.Net
10 matches
Mail list logo
