Hi,
our web site contians
Web Application1 (.net 2.0) = the web stie
Web Application2 (.net 2.0) = virtual directory
Web Application3 (classic ASP) = virtual directory

After we upgraded our server from .net 1.1 to 2.0 the Web Application2 is
very slow (web application1 and web application3 are fast as usual). why?

- all applications use same connection string to communicate with our
database.
- we have installed .net 2.0 and Service Pack 1 for it.

thanks for your help

Re: slow application after upgrading from 1.1 to 2.0 by David

David
Tue May 06 22:13:56 CDT 2008

On May 6, 5:06=A0am, cyrus <cy...@discussions.microsoft.com> wrote:
> Hi,
> our web site contians
> Web Application1 (.net 2.0) =3D the web stie
> =A0 =A0 Web Application2 (.net 2.0) =3D virtual directory
> =A0 =A0 Web Application3 (classic ASP) =3D virtual directory
>
> After we upgraded our server from .net 1.1 to 2.0 the Web Application2 is
> very slow (web application1 and web application3 are fast as usual). why?
>
> - all applications use same connection string to communicate with our
> database.
> - we have installed .net 2.0 and Service Pack 1 for it.
>
> thanks for your help


You should profile your Web Application2 to determine what is actually
going awry. What exactly is slow? As you have shown, it's not
exactly .Net 2.0 that became slow because Web Application1 remained
fast. So, you are interested to determine/profile Web Application2 to
determine why it is slow.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: slow application after upgrading from 1.1 to 2.0 by cyrus

cyrus
Wed May 07 16:44:00 CDT 2008

thanks for your response

when I move my application to a windows xp server (My machine) it is fast.
It means that the problem lies in the server (iis 6.0). isn't it?
I have changed the web site to use asp.net 2.0 in the asp.net tab under
properties of the web site. but under properties of the web sites folder I
can not choose the asp.net 2.0 becasue it is gray out even i have cheched the
asp.net checkbox under server application in the windows componets.

"David Wang" wrote:

> On May 6, 5:06 am, cyrus <cy...@discussions.microsoft.com> wrote:
> > Hi,
> > our web site contians
> > Web Application1 (.net 2.0) = the web stie
> > Web Application2 (.net 2.0) = virtual directory
> > Web Application3 (classic ASP) = virtual directory
> >
> > After we upgraded our server from .net 1.1 to 2.0 the Web Application2 is
> > very slow (web application1 and web application3 are fast as usual). why?
> >
> > - all applications use same connection string to communicate with our
> > database.
> > - we have installed .net 2.0 and Service Pack 1 for it.
> >
> > thanks for your help
>
>
> You should profile your Web Application2 to determine what is actually
> going awry. What exactly is slow? As you have shown, it's not
> exactly .Net 2.0 that became slow because Web Application1 remained
> fast. So, you are interested to determine/profile Web Application2 to
> determine why it is slow.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>

Re: slow application after upgrading from 1.1 to 2.0 by David

David
Wed May 07 22:24:30 CDT 2008

Changing machines doesn't prove anything. You could have a piece of
code in Web Application2 that says "run slowly on IIS6 but fast
everywhere else" and it would result in the same behavior, but
obviously that piece of code would be the problem, not the server.

IIS6 actually has nothing to do with your application or website other
than providing it a process to execute code in, and there's no
performance loss between XP Pro and Windows Server 2003 for code
execution inside of a process.

The ASP.Net checkbox in Windows Components has no relation to the
ASP.Net setting in the Tabs under properties of the website. The
checkbox only ensures to run ASP.Net 1.1 aspnet_regiis.exe, while the
Tab indicates some ScriptMap settings touched by aspnet_regiis.exe.

The best way to figure this out is to profile the application to
determine what action(s) are slow and then determine why. Randomly
changing machines/settings is not an effective way to troubleshoot.
You can make a million random guesses and still not find the right
answer


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On May 7, 2:44=A0pm, cyrus <cy...@discussions.microsoft.com> wrote:
> thanks for your response
>
> when I move my application to a windows xp server (My machine) it is fast.=

> It means that the problem lies in the server (iis 6.0). isn't it?
> I have changed the web site to use asp.net 2.0 in the asp.net tab under
> properties of =A0the web site. but under properties of the web sites folde=
r I
> can not choose the asp.net 2.0 becasue it is gray out even i have cheched =
the
> asp.net checkbox under server application in the windows componets.
>
>
>
> "David Wang" wrote:
> > On May 6, 5:06 am, cyrus <cy...@discussions.microsoft.com> wrote:
> > > Hi,
> > > our web site contians
> > > Web Application1 (.net 2.0) =3D the web stie
> > > =A0 =A0 Web Application2 (.net 2.0) =3D virtual directory
> > > =A0 =A0 Web Application3 (classic ASP) =3D virtual directory
>
> > > After we upgraded our server from .net 1.1 to 2.0 the Web Application2=
is
> > > very slow (web application1 and web application3 are fast as usual). w=
hy?
>
> > > - all applications use same connection string to communicate with our
> > > database.
> > > - we have installed .net 2.0 and Service Pack 1 for it.
>
> > > thanks for your help
>
> > You should profile your Web Application2 to determine what is actually
> > going awry. What exactly is slow? As you have shown, it's not
> > exactly .Net 2.0 that became slow because Web Application1 remained
> > fast. So, you are interested to determine/profile Web Application2 to
> > determine why it is slow.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //- Hide quoted text -
>
> - Show quoted text -