.NET 2.0 Master Pages problem

[Tim Wallace]

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

 

[Guest]

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.

 

[Guest]

Alternatively, you can use Aspnet_regiis.exe which is part of the .NET
framework. See: http://msdn2.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx

 

[Tim Wallace]

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]

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

 

[Juan T. Llibre]

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

That's only needed if you're running Windows 2003 Server.

In any other OS, you don't need to have separate AppPools for 1.1 and 2.0.
Since you're using Windows 2000, don't worry about that.

Denis Bauer's Version Switcher should allow you to
instruct the application to use the .Net Framework 2.0.

It's use is very intuitive. Try it.
Just install it in your Windows 2000 server and run it.

You'll see what you need to do.
Just select your application and the .Net Framework 2.0...and hit the "Switch .Net Framework"
button.

There's an app image here :
http://www.denisbauer.com/NETTools/ASPNETVersionSwitcher.aspx

 

[Tim Wallace]

Page:

I get an error message as soon as your .NET switcher launches.

Tim

 

[Page Brooks]

Tim,
What is the error message you are receiving? I didn't write the application
so I don't know what could be wrong with it. The tool is using Aspnet_regiis
internally so you can always fall back to that if you can't get the switcher
tool to work. I think the -s and -sn command line options for aspnet_regiis
are what you need.

Thanks,
Page Brooks
www.explosivedog.com

 

[Juan T. Llibre]

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.

 

[Tim Wallace]

Page:

It says "ASP.NET Version Switcher has encountered a problem and needs to
close. We are sorry for the inconvenience." It appears to be an
application-defined window, not a stock pop-up.

I'm most concerned that the .NET tab is not being displayed in the
properties window. Also that running aspreg_iis does not do what is
advertised.

Tim

 

[Juan T. Llibre]

re:
!> I think the -s and -sn command line options for aspnet_regiis are what you need.

The -s and -sn options only work for registering scriptmaps,
not for registering/unregistering the .net framework with IIS.

Tim,

Which versions of the .Net Framework have you installed ?
This is very important...

If you *did* install both 1.1 and 2.0, you have a bad install of at least one of them.

To fix both .Net framework installs, run

aspnet_regiis -ua

....from command windows in *both* the 1.1 directory
( Drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 )
and
the 2.0 directory
( Drive:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 )

i.e., you will run the same command *twice*, once from a command window in each directory.

Then, *after* you do that, run

aspnet_regiis -i

from a command window in each of those directories, starting with the 1.1 directory.

Then, run the ASP.NET switcher again. It should run.

 

[Tim Wallace]

Juan:

Thanks for the advice. I have 1.1 and 2.0 installed. I followed your
steps, but the switcher still doesn't work.

Tim

 

[Juan T. Llibre]

re:
!> Thanks for the advice. I have 1.1 and 2.0 installed. I followed your
!> steps, but the switcher still doesn't work.

Then, your only recourse is to fully uninstall/reinstall both .Net Frameworks,
as opposed to only unregistering/reregistering them.

To completely remove the .Net Framework 1.1, see :
http://support.microsoft.com/default.aspx/kb/824643

The .Net Framework 2.0 can be uninstalled from the "Add or Remove Programs" link in Control Panel.

When you reinstall, make sure you start with 1.1

See : http://asp.net.do/faq/basic.aspx for links to the setup files for both.

As a last resort, have you applied the 1.1 Service Pack 1 ?
http://asp.net.do/faq/basic.aspx has the link for that as well.