Oh no problem. It was when your tone turned condescending and insulting, like when you told me,
a professional coder, that "The purpose, when you debug, is to identify problems". No shit.
And then you continued with, 'No, but you may very well be the first one to refuse to debug an
application"
I didn't make a big deal out of it, like you did. I can take a bit of sarcasm, especially from
someone who is trying to help me. But if you're going to dish it out, you better be willing to
take some back.
So, now, besides being in an "ivory tower",
I'm also using the "guise of being helpful",
and I made an "insulting remark" to you ?
If you would quote it, I'd be quick to apologize.
I suspect you are not capable of doing that.
Whatever, Chip. Carry on.
You probably should have not ended the converstation there and actually read the rest of the
post. If an insulting remark were enough to stop conversation, I wouldn't have read past a few
sentences into your third post. If you want to continue to insult people you assume aren't as
intelligent or determined as you are, please just be straight forward and don't use the guise
of being "helpful".
re:
You really need to get down from that ivory tower.
That's the end of this conversation.
I'm sorry I took up your time.
Good luck in your future endeavors.
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.
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.
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
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.
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.
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.
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?
