Click to See Complete Forum and Search --> : ASP and IIS6


Nickson
May 10th, 2004, 06:24 AM
Hi,

I am new to IIS6, but I am in the process of considering to migrate to IIS6 in W2003 for my website which is currently coded in ASP and runned under IIS4 in NT4.0.

I have the following doubts which I really appreciate you experts can help me

1) Can I just migrate over the ASP pages without recoding them. i.e. Can IIS6 execute the ASP pages?

2) Subsequent can I code my new web pages in ASP .NET and old ASP pages and the new ASP .NET pages can interact freely with each other without any interfacing required?

3) I understand that IIS6 has a very very tight security. What are the general implications when migrating the website over?

Really appreciate any answers.

rgds,
Nickson

trekmp
May 11th, 2004, 11:43 AM
I can answer (1) for you.

Yes you can just transfer your current ASP pages onto IIS6, I didn't have any real problems. I think in all I had to make two changes and those were to do with emailing.

As for (2), if I remember this correctly things like session variables, etc cannot be shared between ASP and ASP.NET files, they are two seperate processes. You can mix and match teh files, just remember its not a simple matter to get the two to talk.

Please anyone feel free to correct me on this.

Mutilated1
May 14th, 2004, 10:22 AM
Hi Maybe I can help somewhat... I'm not an expert on ASP.NET by anymeans, but I've been doing classic ASP for years. This is how I would answer your questions based on

To Answer Your Questions:

1. I would agree with trekmp, for the most part classic ASP pages will run fine on IIS6.0. I've never had any real problems at all. A few minor issues perhaps, but mostly nothing to worry about.

2. trekmp is correct, you cannot share the session, but there is an easy solution. If you change the file to .aspx instead of .asp and add the aspcompat='true' directive, you are mostly home free. I would expect that there would be some issues to resolve, because experience tells me that there usually is something that will go wrong when you make any change, but my experience with it has been pleasent and generally unfrustrating. Change the file extension, remove all the Set(s) from your code since Set isn't needed anymore. Add some parenthesis to the method calls since they are required now. I may be forgetting a thing or two, but really thats about all you need to do. Its pretty easy.

3. The security is much improved over previous versions of IIS, but the issues you must deal with are the same. There are some easier ways of doing things now. My feeling for the security issue is that Microsoft is finally beginning to get things right. Coming from NT4.0, IIS 6.0 will still support the same security features you are using, but there are additional security features you can take advantage of as you incorporate more .NET.

Good luck on your migration.