SP 1.1 .NET

  • Thread starter Thread starter Just D.
  • Start date Start date
J

Just D.

I have SP1.1 .NET installed on my development machine where I write the code
and compile it. The production machine doesn't have this service pack for
1.1 .NET. Can it affect my Web Application? I hope that I found a reason of
my issue and I'm trying to understand why same program works in different
ways on two machines with the only one significant difference in this
service pack.

Just D.
 
it could be, but the changes are minor.

I think it more likely to be security setting.
probably you're admin of your computer and your program runs with full
right, whereas on developement machin they run as restricted user.

is it security exception that you get?
 
This is not a security exception. I wrote my own exception handler - it
keeps silence. This is a problem, I even don't know how it appears. The
program asks many questions and finally when the list of questions is empty
it should redirect the customer to another page with thanks and then to the
beginning to a new customer. This is a VERY simplified schema. The problem
is that the program doesn't redirect to the required page but shows the
previous blank page and dies at this stage.

It also uses many redirections and all are working fine. So the problem
shouldn't be there. I tried to use absolute URL to redirect, relative, both
work fine on my machine, but only one redirect doesn't work on production.
It seems I'm crazy.

Just D.
 
Hi Ken,
Yes, there are differences... and some problems:
Service Pack 1 for .NET v1.1 Broke My ASP.NET App
http://weblogs.asp.net/pwilson/archive/2004/09/16/230591.aspx
Click to expand...

"Some problems", sounds cool, but actually more than some problems. Thanks
for this link, I added my comments. That's exactly what I was looking for. A
usual page control refused to work for this reason and not only on my
machine as I see. I have tested another one machine yesterday, my
application even refused to start showing the blank page. So both versions -
i.e. BEFORE SP and WITH SP are incompatible, thanks you M$ developers! This
is a very good gift for all production machines in the whole world.

Just D.
 
It seems pretty much unanimous that someone screwed up with the SP update.
 
I'd really like to know that Microsoft actually has a KB article about this
issue. My systems guy thing that it's an application problem caused by us
developers. My systems guy can say idiotic things sometimes, but for some
reason blogs aren't enough for him.

Do I have to open an ticket with MS to get an official fix?
 
Back
Top