ASP & ASP.Net on the same web server?

[david7777777777]

I've got a Windows 2000 Server running a couple of very basic ASP applications. I want to start developing with ASP.Net. Is it safe to update my web server to ASP.Net framework or should I use a separate server for the .Net stuff? I'm wondering if my current ASP applications will still work if I install the .Net stuff onto that server. Thanks.

 

[bigfoot]

ASP.NET and ASP will get along nicely on the same server. I have both operational on the same server.

The reason for this is because asp.net pages end with .aspx and the server knows which dll to send it to - asp or asp.net.

-Gary

 

[david7777777777]

Awesome! Thanks. Did you have to modify your existing ASP pages to allow them to work under the .Net framework?

 

[bigfoot]

Yes. ASP.NET only takes the name. With all I am finding, everything has changed but the name.

It's like writing a program not a web page. It's really great. And you can compile the code behind the pages too.

 

[david7777777777]

Can you tell me where I could see some examples of exactly what types of things I'd have to change in my existing ASP pages please? This will determine if I have the time to go to .Net right now under my current deadlines, but I'd really like to start using .Net so I hope the needed changes are slight. Thanks.

 

[bassguy]

David,
there is no no no upgrade path from asp to aspx. they are as similar as a gas engine and a deisel engine.

you are better off to just start playing with aspx and learn it and leave your old apps running in asp.

just my opinion

bassguy

 

[david7777777777]

bassguy,
I agree and I am learning ASP .Net as we chat as fast as I can, reading the

http://www.w3schools.com

articles at the moment. But my concern is that if I install the .Net framework onto my existing production Windows 2000 web & SQL 2000 server, my two existing classic ASP applications on that server will no longer function without some code modifications. So I'm trying to get a feel for exactly how much modification will be required. So far I haven't been able to find one example of exactly what I'd have to modify in my exsisting classic ASP code pages after installing .Net on the server. Thanks.

 

[bassguy]

David, Asp files use the extension .asp and .net ones use .aspx there is no overlap at all

 

[david7777777777]

This is from

http://www.weschools.com:

"ASP .NET is not fully compatible with earlier versions of ASP, so most of the old ASP code will need some changes to run under ASP .NET.

To overcome this problem, ASP .NET uses a new file extension ".aspx". This will make ASP .NET applications able to run side by side with standard ASP applications on the same server."

So based on what you're telling me plus what this statement says, am I to understand that as long as I do not want to add any ASP.Net functionality to my existing ASP applications or change them in any way (which is true), I can just leave them alone, install the .Net frame work onto the same web server, publish new ASP.Net applications onto that same server, and expect both my classic ASP and new ASP.Net applications to work correctly in theroy?

 

[bassguy]

Yup, I do it all the time


bassguy

 

[bigfoot]

We have the .NET framework installed, but I am still using the old ASP on all of my pages. It looks for the .aspx extention to send it to the .NET dll for processing, so go ahead and load it, and play all you want. It will not effect the org. ASP.

You're safe. And I thought the same thing.: