What to expect when upgrading to IIS 6.0

[Guest]

Hi,

Can any one point me to a good resource on what to expect for .NET
Applications when upgrading from IIS 5.0 to IIS 6.0

We are thinking to move to IIS 6.0 but fear......

Thanks,

 

[Juan T. Llibre]

Fear not...

You'll get more features, security and performance.
You'll also get many more administration options.

Here's a good summary of IIS 6.0's new features :

http://www.microsoft.com/windowsserver2003/evaluation/overview/technologies/iis.mspx

And here :
http://download.microsoft.com/download/8/a/7/8a700c68-d1af-4c8d-b11e-5f974636a7dc/IISOverview.doc
is IIS 6.0's Technical Overview

 

[Scott Allen]

I have a couple areas to watch in regards to ASP.NET applications:

Moving ASP.NET Apps from IIS 5.x to 6.0
http://odetocode.com/Blogs/scott/archive/2005/07/10/1925.aspx

 

[Kevin Spencer]

Application Pooling is awesome!

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
The sun never sets on
the Kingdom of Heaven

 

[Guest]

Yeh I know its ALL SUPER AND GREAT....
but , What I'm really looking for is things that would break for existing
..net applications.

Thnx.

 

[Scott Allen]

That's what the link I provided earlier tries to help with. Most of
the problems people see are because of changes in the worker process
model. The wp in IIS 6 runs under a different account, has different
configuration defaults, and is configured using a different
configuration section.

 

[Juan T. Llibre]

re:

What I'm really looking for is things that would
break for existing .net applications.

Why didn't you say so ?



Question for you :

Why would you think *anything* would break, at the IIS level,
when you migrate from IIS 5.0 to IIS 6.0 ?

I can think about any number of things which could break
when upgrading a .Net Framework, for example, but I can't
think of even one thing which IIS could break in an application.

Can you give me an example of what you fear might break ?

 

[Guest]

Thanks Scott, I did go through the document and have noted the issues you
mentioned and hopefully would be a smooth transition

Regards

 

[Guest]

As Scott Mentioned the change in name of ASP.NET account could break an
application which is trying to access files and folders on other machines,
because of permissions etc.

 

[Juan T. Llibre]

Yup...but that an *ASP.NET* feature, not an IIS feature.

It was *ASP.NET* which changed it's identity. Not IIS.

Nothing changed in IIS. What changed is within ASP.NET.
I just can't think oif anything which would break at the IIS level.

When a new Application is created in IIS 6.0, all the configuration
properties have default values which won't break anything in
*any* existing ASP.NET application.

*You* ( meaning any IIS user ) can screw them up,
by changing them to non-default values, but IIS won't.