My employer has a website built in classic ASP. It has about 50 pages showing data from SQL Server. I have experience with ASP.NET, mostly versions 1 and 2. My supervisor is trying to convince the CEO to approve a project to convert the website to ASP.NET.
What are the advantages/disadvantages? If we convert should we start with the Migration Assistant for ASP.NET 1.1? Should we migrate all the way to 4.0? Should we use MVC? Should we create a web application? Should we wait for Microsoft to dump ASP.NET
and move to HTML5? Should we convert the SQL code to LINQ? I don't like LINQ and I've read someone else who said it's SQL for dummies.
My employer has a website built in classic ASP. It has about 50 pages showing data from SQL Server. I have experience with ASP.NET, mostly versions 1 and 2. My supervisor is trying to convince the CEO to approve a project to convert the website to ASP.NET.
Why does he want to convert the website? If it works, why would you convert it. If it needs some minor modifications, I would do that in Classic ASP. If it needs a major update, I think you should convert the website.
If we convert should we start with the Migration Assistant for ASP.NET 1.1?
No. start form scratch
DallasSteve
Should we migrate all the way to 4.0?
Why not?
DallasSteve
Should we use MVC? Should we create a web application? Should we wait for Microsoft to dump ASP.NET and move to HTML5? Should we convert the SQL code to LINQ? I don't like LINQ and I've read someone else who said it's SQL for dummies.
It's all up to you. If you don't like LINQ, don't use it. If you like MVC, go for it. And waiting for Microsoft to dump ASP.NET and mover to HTML5 will probably take a long time, becuase this doesn't make any sence at all....
The advantage of not migrating is that you don't have to do anything. If you have the skillset to upgrade/fix problems, then what's the point in changing. The advantage of migrating is that you have a rich programming framework to play with.
If you do migrate, I suggest MVC, as there are similarities with Classic ASP (in the View). If you go with MVC it is, by its very nature, a Web Application. If you go down the route of WebForms, I'd go straight to v4.0.
Microsoft won't 'dump' ASP.NET and move to HTML 5 because they're two different technologies. HTML 5 is simply markup. ASP.NET is a programming framework.
Regarding converting from SQL to LINQ, if you've already got the SQL then why bother. LINQ is useful, if you're starting from scratch. Whether it's SQL for dummies is just a matter of opinion. I use SQL and LINQ and don't see the basis for that opinion.
Ultimately it depends on what's the right tool for the job. Some people just don't like change and then criticise new technologies that come along purely on that basis.
DallasSteve
Member
221 Points
331 Posts
What To Do With An Old ASP Website
Feb 16, 2012 04:40 PM|LINK
My employer has a website built in classic ASP. It has about 50 pages showing data from SQL Server. I have experience with ASP.NET, mostly versions 1 and 2. My supervisor is trying to convince the CEO to approve a project to convert the website to ASP.NET.
What are the advantages/disadvantages? If we convert should we start with the Migration Assistant for ASP.NET 1.1? Should we migrate all the way to 4.0? Should we use MVC? Should we create a web application? Should we wait for Microsoft to dump ASP.NET and move to HTML5? Should we convert the SQL code to LINQ? I don't like LINQ and I've read someone else who said it's SQL for dummies.
Thanks for your thoughts
www.SteveGaines.us
hans_v
All-Star
35986 Points
6550 Posts
Re: What To Do With An Old ASP Website
Feb 16, 2012 04:58 PM|LINK
Why does he want to convert the website? If it works, why would you convert it. If it needs some minor modifications, I would do that in Classic ASP. If it needs a major update, I think you should convert the website.
http://www.beansoftware.com/ASP.NET-Tutorials/Classic-ASP-vs-ASP.NET.aspx
No. start form scratch
Why not?
It's all up to you. If you don't like LINQ, don't use it. If you like MVC, go for it. And waiting for Microsoft to dump ASP.NET and mover to HTML5 will probably take a long time, becuase this doesn't make any sence at all....
stevenbey
All-Star
16526 Points
3378 Posts
Re: What To Do With An Old ASP Website
Feb 16, 2012 05:00 PM|LINK
Wow, lots of questions! ;)
The advantage of not migrating is that you don't have to do anything. If you have the skillset to upgrade/fix problems, then what's the point in changing. The advantage of migrating is that you have a rich programming framework to play with.
If you do migrate, I suggest MVC, as there are similarities with Classic ASP (in the View). If you go with MVC it is, by its very nature, a Web Application. If you go down the route of WebForms, I'd go straight to v4.0.
Microsoft won't 'dump' ASP.NET and move to HTML 5 because they're two different technologies. HTML 5 is simply markup. ASP.NET is a programming framework.
Regarding converting from SQL to LINQ, if you've already got the SQL then why bother. LINQ is useful, if you're starting from scratch. Whether it's SQL for dummies is just a matter of opinion. I use SQL and LINQ and don't see the basis for that opinion. Ultimately it depends on what's the right tool for the job. Some people just don't like change and then criticise new technologies that come along purely on that basis.
Hope that helps!
http://stevenbey.com
Recursion: see Recursion