Thread question

[Alvin Bruney [MVP]]

Agreed but I can't reproduce it. All I have is newsgroup threads to go on.
This may not be enough.

--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok

Alvin, JD,

JD is absolutely right, this is a bug in V1.1, HttpException should be
marked Serializable, and this exception is hiding the real problem. One
possible causes could be a viewstate validation error, "viewstate
validation" code seems to run in a separate app domain on IIS6.
Alvin, I would suggest you to contact PSS and check with them if no hotfix
is available for this issue (the HttpException).

Willy.

i believe my comments were qualified to say that it may or may not
happen
depending on underlying OS.

True. Are you using IIS 6.0 IIS 5.0? Different models between them. I was
testing on IIS 5.0.

From the error message it looks like the exception is coming from another
app domain or process. Funny HttpException isn't marked as serializable,
since thats one of the first things you learn with .NET exceptions, make
them serializable since you don't know when your exception may cross app
domain boundaries. The class HttpException inherits from,
System.Runtime.InteropServices.ExternalException, is serializable but
HttpException is not. I might consider the lack of serializable marker on
that exception a bug, but either way this error probably preventing you
from
seeing the true error.

What I would attempt to do is attach the debugger to the asp.net process,
there is a way to set the debugger to break on any exception thrown,
there
might even be a way to filter for specific exception, I can't remember
from
the steps from memory and I'm not sitting on a computer with VS.NET, and
this is something I haven't done for quite a while. At the point the
exception is thrown the debugger will break, start inspecting the memory
at
the point and see if you can make heads or tails out of it. Basically you
just need the message from the HttpException before you get the not
serializable exception. Its a tough task if you have never done stuff
like
this before but if you get through it you will learn a bunch. I suggest
John
Robbins book on debugging.

I agree with you too on the lack of documentation on multi-threading in
ASP.NET applications.

Good Luck,
JD

The type System.Web.HttpException
in Assembly System.Web, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a is not
marked as serializable

--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
<"Alvin Bruney [MVP]" <vapor at steaming post office>> wrote:
i believe my comments were qualified to say that it may or may not happen
depending on underlying OS.

I can't reproduce it either, at least for now. I know I am not insane
because I've found a couple of threads on the newsgroups which
produced
this
exception.

What's the message of the exception?