|
ASP.Net and IIS (ASPX Extension Not Registered)
There might be
situations where IIS is not recognizing pages with ASPX extensions in
your website even if the dotnet framework is installed in your system.
This usually happens
when you have installed dotnet frame work first and then installed the
IIS in your system. In this case, ASP.Net will not be registered in your
IIS.
To register ASP.Net with
IIS all you have to do is, goto your DotNet command prompt (usually this
will be in the Visual Studio Tools menu of your Visual Studio.Net Menu
in your Starup Menu) and type aspnet_regiis -i
aspnet_regiis is a
command line tool which registers ASP.Net with IIS. You can also use
this tool to unregister ASP.Net with IIS by specifying
aspnet_regiis -u
But beware!! while
running aspnet_regiis -i on a live
production site consider the following factors too!!
-
aspnet_regiis -i
associates every website in the IIS
with the dotnet framework. Note that every version of dotnet
framework has its own version of aspnet_regiis
which registers IIS with that version of dotnet framework.
So if you have two websites in your IIS, one running on v1.1 of
dotnet framework and the other running on version 2.0 of dotnet
framework, and if you run aspnet_regiis -i
from v2.0 of dotnet framework, then even the site running on
v1.1. of dotnet framework will be associated with v2.0 !! So do not
run this command in the above form (i,e. with -i switch) on IIS
which has websites running on different versions of dotnet
framework.
-
Running
aspnet_regiis -i
also affects the auto generated values
of form based logins and view state checksums by resetting them with
immediate effect. This means that, running the command in the above
form will affect all users who are currently logged into your IIS!
Hence, this command (aspnet_regiis -i)
should not be run when there are active user sessions in your IIS.
-by Gurudev
MADE IN
INDIA
gurudevp@vsnl.net
On 05 August 2005
Home
>> Computers >> Programming
>> Dotnet
|