Migration of classic Asp, Asp.Net 1.1 Framework to 4.5 Framework - Tools & Best Practices Details required

Question

0.00/5 (No votes)

See more:

Set of Major Web Applications has to be migrated from legacy Microsoft technologies to latest .Net 4.5 Framework.

Class ASP (VB Script), Asp.Net 1.1 Framework applications has to be migrated to 4.5 Framework (Applications includes Website project type and Web application project types)

Automated Tools or Best Practices are required for Analysis and Migration activities.

Analysis: The following details has to identified for each legacy applications
(Asp (VBScript), Asp.Net 1.1, 2.0, 3.5) - No of classes, Methods, Lines of codes, DLL’s & Third Party Libraries, Complexity, Level of Effort . Information about Tools that can generate the planning level information is required.

Migration: Tools recommended for migration, Best Practices from earlier migrations, any automated solutions, etc...

Please help to share your thoughts and inputs.

Posted 24-Mar-15 3:23am

Sara_vanan_M

Add a Solution

Comments

Richard Deeming 24-Mar-15 9:31am

There's no simple or automated way to migrate "classic" ASP applications to ASP.NET; you'll need to re-write them.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

F-ES Sitecore · Answer 1 · 2015-03-24T03:31:00

Solution 1

To be honest you're going to have to just rewrite this from scratch; you're trying to convert an apple into a vacuum cleaner. If you are using any databases then you can keep those and simply connect to them as before, but pretty much everything else is going to change.

To preempt your next question, migrating bit by bit isn't really an option either, you're best to do it in one go.

Posted 24-Mar-15 3:31am

F-ES Sitecore

Comments

Sara_vanan_M 24-Mar-15 9:54am

Basically at first I am looking in to analysis tools that will give me planning level information.

Analysis: The following details has to identified for each legacy applications
(Asp (VBScript), Asp.Net 1.1, 2.0, 3.5) - No of classes, Methods, Lines of codes, DLL’s & Third Party Libraries, Complexity, Level of Effort . Information about Tools that can generate the planning level information is required.

If you come across any pls share..

F-ES Sitecore 24-Mar-15 10:08am

If you've been asked to gather that data then fair enough, but I doubt it has much relevance. It certainly won't be worth the time it will take to collect as there is no correlation between Classic ASP effort and asp.net effort.

I imagine you could knock up a script to count number of lines\methods\classes quite easily.