Re: .NET 2.0 Master Pages problem

Tech-Archive recommends: Fix windows errors by optimizing your registry



re:
IIS can only run one version of ASP.NET at a time in each app pool.

That's only true for IIS 6.0, which only comes with Windows 2003 Server.



Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Page Brooks" <NOSPAMpagebrooks@xxxxxxxxx> wrote in message
news:uRUjE1NiHHA.4976@xxxxxxxxxxxxxxxxxxxxxxx
Tim,
No problem. Just to make sure, did you run aspnet_regiis -i from the v2.0.x folder? I've run
into situations before where I could not get the ASP.NET tab to show up in IIS, but ASP.NET would
still work correctly.

About the Application Pooling Issue:
IIS can only run one version of ASP.NET at a time in each app pool. So, if you have existing
ASP.NET 1.x applications and you decide to configure a new ASP.NET 2.0 application under the same
App Pool. The ASP.NET 1.x applications will start throwing exceptions.

Check out this link for more details:
http://msdn2.microsoft.com/en-us/library/1kdfe21k(VS.71).aspx

Thanks,
Page Brooks
www.explosivedog.com


"Tim Wallace" <twallace-ThisDoesNotBelong-AT-emailDOTcom> wrote in message
news:OOIoruNiHHA.3808@xxxxxxxxxxxxxxxxxxxxxxx
Page:

Thanks for the response. I already ran aspnet_regiis -i. No joy. I'll give your app a whirl
and see if that helps.

I'm unfamiliar with the separate AppPools issue. Can you give me some guidance with that,
please?

Tim

"Page Brooks" <NOSPAMpagebrooks@xxxxxxxxx> wrote in message
news:A515F9FA-AC0C-48A6-A020-22CB86CB2456@xxxxxxxxxxxxxxxx
I've run into this problem before. You can try running this little utility
to switch the version of ASP.NET for a specific web application:

http://www.denisbauer.com/NETTools.aspx

Please be aware that you need seperate AppPools for each version of ASP.NET
that you are running. I've seen this unexpectedly bring down many
applications before.
--
Thanks,
Page Brooks
www.explosivedog.com


"Tim Wallace" wrote:

I have a windows 2000 server on which I have installed the .NET 2.0
Framework runtime. I have an application I've written using VS 2005. In
it, I use master pages. When I debug this app on my machine, it looks
great. When I run it on the server, it looks like crap - no master page
goodness is being employed. This is the first ASP.NET 2.0 application I've
put on the server. I noticed that there is no ASP.NET tab on the properties
window as there is on never Windows server editions. How can I tell IIS
that this application should be run as ASP.NET 2.0?

Tim









.



Relevant Pages

  • Re: IIS Start up errors
    ... provide the detailed steps to reinstall the IIS server in SBS 2003 server. ... For example, programs such as Microsoft ... In the Currently installed programs list, click Windows Small Business ...
    (microsoft.public.windows.server.sbs)
  • Re: Active Directory Services cannot find the web server
    ... I am having the same problem with a windows xp pro with iis 5.1 ... incedently does not work properly when connecting to the server. ... both the client and server and still no luck. ...
    (microsoft.public.dotnet.faqs)
  • Re: restated: VS Develper (non Admin) missing IIS MMC Management
    ... > debug ASP in VB.Net, and of course manage IIS MMC. ... > Microsoft Development Environment ... > Information Server on the client and the server. ... > server from a Windows NT 4.0 client. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: restated: VS Develper (non Admin) missing IIS MMC Management
    ... > debug ASP in VB.Net, and of course manage IIS MMC. ... > Microsoft Development Environment ... > Information Server on the client and the server. ... > server from a Windows NT 4.0 client. ...
    (microsoft.public.dotnet.general)
  • Re: restated: VS Develper (non Admin) missing IIS MMC Management
    ... > debug ASP in VB.Net, and of course manage IIS MMC. ... > Microsoft Development Environment ... > Information Server on the client and the server. ... > server from a Windows NT 4.0 client. ...
    (microsoft.public.inetserver.iis)