Re: IIS ASP.NET 2.0 Bug
- From: "Chip" <chip@xxxxxxxxxxxxx>
- Date: Thu, 23 Mar 2006 09:29:44 -0800
You really need to get down from that ivory tower. Do you think I'm just
sitting here waiting for the app to fix itself? I am taking the most
reasonable, logical, and efficient way to fixing this. I first identified
that the problem is with IIS and not my code. So I posted the issue to see
if there was any buzz on it or a work around that I need to know about AND
to alert others and MS about the problem.
Before I spend hours of my time to isolate which part of ISS is breaking,
just so I can give that info to MS and save them some time (and not even
necessarily figure out if there IS a work around), I would like to know if
there is a likely cause so I can concentrate my efforts in the right area.
"Juan T. Llibre" <nomailreplies@xxxxxxxxxxx> wrote in message
news:%23W8WrwpTGHA.4520@xxxxxxxxxxxxxxxxxxxxxxx
re:
You are CLOSE to right. Debugging is something you do to identify the
problem SO YOU CAN FIX IT. I will obviously not be fixing IIS even if I
do figure it out.
I guess you won't fix your problem, then.
The idea, when debugging, even if you can't fix the problem by yourself,
is reporting what the debugger says the problem is.
Someone might have the necessary experience to know what to do.
But if you won't even debug your own application,
there's nothing anybody can do to help you further.
This may not be about "fixing IIS". Something else might be the problem.
Debugging your application might tell what the problem is.
In any case, at this point, you would be the one benefitting from the
collective
knowledge that frequenters to this newsgroup have, but if you won't help
yourself, nobody can do it for you.
re:
I did appreciate your help in telling me how to turn Casini off.
You're quite welcome.
Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Chip" <chip@xxxxxxxxxxxxx> wrote in message
news:O8cEZepTGHA.4264@xxxxxxxxxxxxxxxxxxxxxxx
Argh yourself. You are CLOSE to right. Debugging is something you do to
identify the problem SO YOU CAN FIX IT. I will obviously not be fixing
IIS even if I do figure it out. Yes, I obviously need to figure out a
work around, but my preferred solution woulld have been, "Oh, MS has
identified that bug and here is the fix". I am not looking forward to
debugging a platform I cannot see into and deals with multi-threading.
I did appreciate your help in telling me how to turn Casini off.
Chip
"Juan T. Llibre" <nomailreplies@xxxxxxxxxxx> wrote in message
news:uJ2glVnTGHA.776@xxxxxxxxxxxxxxxxxxxxxxx
re:
Debugging would seem to be a little useless since, as I said, it runs
perfectly under Casini. The
problem is not with my code, but with the difference between IIS and
Casini.
Aargh!
The purpose, when you debug, is to identify problems.
If you debug the application under IIS,
you will identify what's causing the problems you say you have.
Isn't that what you want to do ? [ identify the problem(s)... ]
re:
I can't be the first and only person to notice a difference between the
two environments.
No, but you may very well be the first one to refuse to debug an
application
which apparently is having problems running uder IIS.
You can't pin down execution problems via osmosis.
Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Chip" <chip@xxxxxxxxxxxxx> wrote in message
news:OocyajkTGHA.5500@xxxxxxxxxxxxxxxxxxxxxxx
Debugging would seem to be a little useless since, as I said, it runs
perfectly under Casini. The
problem is not with my code, but with the difference between IIS and
Casini. It appears there is a
bug in IIS. I can't be the first and only person to notice a difference
between the two
environments.
"Juan T. Llibre" <nomailreplies@xxxxxxxxxxx> wrote in message
news:eWuapyjTGHA.1572@xxxxxxxxxxxxxxxxxxxxxxx
Have you tried debugging the app under IIS ?
Post some of the code that's failing in IIS.
That's the only way we could possibly help you.
Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Chip" <chip@xxxxxxxxxxxxx> wrote in message
news:usPpLcjTGHA.5552@xxxxxxxxxxxxxxxxxxxxxxx
I have a dual-threaded app that runs just as it's supposed to under
Casini. However, when I run
the exact same code undier IIS (ASP.NET 2.0) on the same machine, it
is totally unpredictable and
crashes the server. One would think my threading was the problem, but
like I said, runs perfectly
under Casini.
Any ideas?
.
- Follow-Ups:
- Re: IIS ASP.NET 2.0 Bug
- From: Juan T. Llibre
- Re: IIS ASP.NET 2.0 Bug
- References:
- IIS ASP.NET 2.0 Bug
- From: Chip
- Re: IIS ASP.NET 2.0 Bug
- From: Juan T. Llibre
- IIS ASP.NET 2.0 Bug
- Prev by Date: Question on building projects using VS .NET
- Next by Date: Re: how make a textbox enabled false without postbac k
- Previous by thread: Re: IIS ASP.NET 2.0 Bug
- Next by thread: Re: IIS ASP.NET 2.0 Bug
- Index(es):
Relevant Pages
|