Converting ASP to ASP.NET - Easy or hard?

I have a client who's site is done in ASP... they want to add a lot of e开发者_如何学Cxtra functionality to the site but I don't think it's worth it to keep developing in Classic ASP & they should move to either .NET or PHP.

I don't know much about .NET so was wondering if ASP code can be converted to .NET code at all & if so how much effort is involved in it?

Edit: What's this all about? http://msdn.microsoft.com/en-us/library/ms973813.aspx

---

I don't know much about .NET so was wondering if ASP code can be converted to .NET code at all & if so how much effort is involved in it?

There is pretty much nothing in common between the two. You are most likely looking at a full rewrite to do the upgrade. Really keeping it in Classic ASP is going to start hampering their ability to expand the site. Visual Basic 6 (non-.Net) isn't around anymore (assuming the core logic is written in compiled VB dlls) and won't run in an x64 IIS instance.

---

ASP.NET was a big departure from ASP. However, I disagree with what everyone else seems to be saying.

In 2002 I converted a large ASP website to ASP.NET. If you're going from VBScript to VB.NET, then in fact there is a lot of legacy functionality that's carried over. You don't even have to adopt the codebehind architecture common to ASP.NET web forms if you don't want to. You can even use the classic <!--#include--> files just as you did with ASP.

I mean, there's a lot that will break when migrating to ASP.NET. Data access, for example, is completely different. But there's also a lot that can be carried over.

So you've got two options:

1. Dive in and see what breaks with minimal changes. This may not sound wise, but it's what I did. And with Visual Studio helping you along with compile-time errors, you should be able to finish the project a lot faster this way.
2. Rewrite from scratch doing things the new ASP.NET way. This will allow you to bill for more time, and make your application a little more future-proof.

In all honesty I'd prefer option #2 today. But I thought you should know that conversion is possible (and with less work overall).

---

There is no way you successfully convert a ASP site into a ASP.NET or ASP.NET MVC website.

However, you can reuse HTML and images and such, even though it might be outdated.

---

They're nothing alike. You'd have to manually recode it in the new language.

This probably sounds hard to do, but it's worth learning a modern server-side language.

Whether it's worth it in this specific instance depends on how complicated the site in question is.

---

Check this Microsoft's presentation on how to migrate an ASP application to ASP.NET 2.0.

To summarize, that's not going to be straightforward, even though they present some "if you are short on time" migration tactics.