Convert ASP to ASP.NET?

[kevinj]

Up until now I've been using ASP primarily for the sites I develop. I'm considering converting my ASP to ASP.NET but have not had any experience with .NET. Does anyone have any advice on whether it would be advantageous to convert my pages and if so, could you point me in the right direction to learn about doing so?

[martyt]

Seems to me that if you don't know *why* you need to change, then you probably *don't* need to change...

There are a lot of good articles about converting from ASP to .NET on the Microsoft ASP.NET web site -- www.asp.net -- and on MSDN [msdn.microsoft.com...]

If you don't need to leverage the new features of .NET, there's no reason to migrate unless you just want the experience and want to learn some new stuff. If you have production deadlines to meet, stick with what you know and tinker with .NET on the side.

[too much information]

Now that I have decided to really beef up my site with features, I have found that .NET has functions already built in that I would have to really work on otherwise. Is .NET similar enough to classic ASP that I could migrate fairly easily?

Or even better, can I mix the two? Is it OK to leave my ASP stuff alone and integrate a page or two of .NET in with it?

I took a look at www.asp.net but it doesn't answer that question for me.

Thanks

[RossWal]

TMI,
Sure you can mix the two. One gotcha to be aware of is they can't share session variables. Also, I believe you could rename a .asp page to .aspx and you would have converted, sort of.

[too much information]

I'm not worried about the session variables for the area that I would need the .NET stuff, I'm using forms for that portion of the site so no problem.

I was asking because my host supports ASP but also has a plan specifically for .NET and I was not sure if that ment I would have to convert the entire site. (I am already running up on a deadline and that would be a nightmare!)

Thanks for the info

[chrisv]

I agree with the members who recommend to leave your site as is, ASP, especially if you have a deadline.

There are a lot of language differences between VBScript and VB.NET, and also between JScript and JScript.NET. I would recommend .NET for any new development over ASP, or if your site is running excruciatingly slow, ASP.NET can give you a big boost. But VBScript and JScript are loosely-typed languages, and VB.Net and JScript.Net are strongly-typed (like C++, Java, VB w/Option Explicit, etc.). You will probably find that you've got more variables than Dim (or var) statements!

Database access are also a lot different (for the better) in ASP.Net, and while you can use the same old ADODB.Recordset that you're used to, you're just adding another layer of execution without much in return by simply converting your existing code to ASP.NET