- From Now onward I will describe one Example To deploy your ASP.Net websites.
Step 1: From Visual Studio Published Your Web Application .
Step 2: Copy The Published Application Folder to "C:\intepub\wwwroot" [default] Folder.
Step 3: From RUN - > inetmgr -> OK
Following Screen Will Come . This is the main Page for Any Application. There are Three Panel.
"TestWeb" is recently pasted webapplication on your wwwroot folder.
Step 4 : We need to Convert it to Application , just RightClick and and Then Click on "ConvertToApplication" as Following picture
After Converting it to Application its icon will be
changed and then you can set the property for your web application from
middle pane. you can set IIS Authentication Mode, Default Page Just
like IIS 6.0
You can Change Security Settings on Authentication
Section. Bydefault Setting will be set from your web.config itself. As
in my web.config Form Authentication was set that's why, Forms
Authentication has been Enabled. if we want to change the Status just
double click and update status to Enabled to Disabled or Vice Versa.
Now one most important part to Set Application Pool for you application.
A site can contain many applications including that
site’s default application, which is called the root application. In
addition to belonging to a site, an application belongs to an
application pool, which isolates the application from applications in
other application pools on the server .
Step 1: Right Click on Application Pool and Give the Name of your Pool here i have given "pool" and select Framework and click on OK
Step 2 : if you are writting some
thing on server [ May be writes Error Events Logs ] , you need to
Change the Pool Identity to Local System . Right Click on Pool Identity
set seeting as following image
There are Three Identity of Application Pool
Now , we need to assign the Application Pool to our web application
Step 1: Right Click on "TestWeb" Application and Select "Advanced Settings"
Step 2: Finaly Assign Your Created Application Pool "pool" to "TestWeb" Application.
Now you can run your application by just typing http:\\localhost\testweb and it can be accessable on network by ip also.
I have split this section with some Parts , these are
Application pools used to separate set of IIS worker
processes that share the same configuration. Application pools enable
us to isolate our web application for better security, reliability, and
availability. The worker process serves as the process boundary that
separates each application pool so that when one worker process or
application is having an issue, other applications or worker processes
are not affected.
Fig : Application Pool With Worker Process On IIS Server
In your IIS there may be more than on Web sites hosted
and by creating Application Pool , you can just Assign a Separate
Worker Process to your application. I have already discussed how you
can assign Application Pool To your web application
There are Two Predefined Applocation Pool is IIS 7.0
None of Application Pool Installed bydefault when IIS
7.0 is installed. Classic Application Pool is installed when Asp.Net
2.0 is installed in the System
Application pool identity configuration is an important
aspect of security in IIS 7.0, because it determines the identity of
the worker process when the process is accessing resource. This
Settings comes form IIS 6.0. in IIS 5.0 There Application pool runs
under the local system account. In IIS 7.0 there are Three predefine
Identity , that are same with IIS 6.0
LocalSystem is a built-in account that has
administrative privileges onthe server. It can access both
local and remote resources
||LocalServices Built-in account has privileges
of an authenticated local user account . It does not have any network
||This is the default Identity of Application
Pool NetworkServices has privileges of authenticated local user
aaccount and it can have access remote resource as machine account.
This has been already discussed
Creating Application Pool And Assign it to a Web Application
By default Each Application Pool runs with a Single
Worker Process (W3Wp.exe) . We can Assign multiple Worker Process With
a Single Application Pool.
An Application Poll with multiple Worker process called "Web Gardens" .
Many worker processes with same Application Pool can sometimes provide
better throughput performance and application response time. And Each
Worker Process Should have there own Thread and Own Memory space.
Fig: General Block Diagaram of Web Garden
As Given in Picture, in IIS Server there may be
multiple Applicationpool and each application pool having at least a
single Worker Process. Web Garden should contain multiple Worker
There are some Certain Restriction to use Web Garden
with your web application. If we use Session Mode to "in proc" , our
application will not work correctly because session will be handled by
different Worker Process. For Avoid this Type of problem we should have
to use Session Mode "out proc" and we can use "Session State Server" or
"SQL-Server Session State".
Main Advantage : The worker processes in a
Web garden share the requests that arrive for that particular
application pool. If a worker process fails, another worker process can
continue to process requests.
Create a New Application Pool. Right Click -> Advance Setting -> Go To Process Model Section , Set the Value for Maximum Worker Process
It not always recommended to use Web Garden To Your
Application affects to performance of your sites except in very
specific cases like some long running Synchronous request or
Application is very unstable .
Main Advantages of IIS 7.0 is Modular Design. Which
gives some benefits fo to IIS 7.0 over IIS 6.0. Followin table showing
you some difference of IIS 6.0 and IIS 7.0 .
||Most Features Installed
||Minimum installtion based on role
||ISAPI Filter and ISAPI Extention
||Added Module and handler in managed or native code
||Customize for .NET
There are many more Difference are There.
IIS 7.0 Will Not available with All Operating System . There are some Specific OS and Specific Version For IIS 7.0 .
|Operating System With Edition
|Windows Server 2008
|Windows Vista (Home Basic)
||No (Default) Need to be Install
|Windows Vista (Home Premium)
||No (Default ) Need to be install
|Windows Vista (Business)
|Windows Vista ( Ultimate )