Do we hav any tool to convert asp code to asp.net code?

Please suggest ....

nope....

1) rewrite it.
2) pay somone to rewrite it.

That's about it........

I checked this link

http://www.15seconds.com/News/News.asp?News_Id=550

Being a MVP you should know this. Please suggest if such tool exist.

Here you go..But it has some limitations.

http://www.asp.net/downloads/archived/migration-assistants/asp-to-aspnet/

http://msdn.microsoft.com/en-us/library/ms973813.aspx

chandrashekarthota:

I checked this link

http://www.15seconds.com/News/News.asp?News_Id=550

 

Being a MVP you should know this. Please suggest if such tool exist.

1) it doesnt work well and

2) you are out of line with such a comment. I wish you the best in future endeavors but you will receive no assistance from me again.

Curt,

I am sorry for my reply. After googling i finally found its hard to get a tool.

With your words I am really planning to Create a converter. Any plans to join me..?

I will start researching common things in both asp and asp.net which can be replaced and for functional things and like to store them in database and retrive them with some extra tough logic.

Thanks in advance if you join me.

Chandra Shekar Thota

Visual Developer Asp.Net MVP(since 2006)

chandrashekarthota:

Curt,

I am sorry for my reply. After googling i finally found its hard to get a tool.

With your words I am really planning to Create a converter. Any plans to join me..?

I will start researching common things in both asp and asp.net which can be replaced and for functional things and like to store them in database and retrive them with some extra tough logic.

Thanks in advance if you join me.

Chandra Shekar Thota

Visual Developer Asp.Net MVP(since 2006)

Microsoft themselves gave up on the converter as the two frameworks (if you can call Classic ASP a framework) as just so vastly different that it's just not worth the effort.

There's almost nothing common between asp and asp.net - and the things that are have multiple implementations in asp.net.

Take something simple, like a page with a load of inline <%= variable %> tags - how do you start converting that to use labels? How do you give the labels a meaningful name?

Besides which a straight no-fuss automated migration of asp to asp.net will not yield ANY benefits at all, you might as well keep it in classic ASP, and in many ways the asp.net version will be inferior:

1. Non-optimal use of framework

2. automatically generated variable names lead to code which is hard to read and even harder to understand

3. it'll be undocumented

4. if it's automated no-one will really understand what the new code is doing.

If you check this forum, there's always people wanting a short-cut from classic to .net - and it's just not going to happen - it's not an upgrade, it's a whole new way of writing web applications.

This may sound like a problem, but it isn't really - if you have a really large classic asp application that needs supporting, then just support it, classic asp support from Microsoft isn't going to go away any time soon...

http://www.netcoole.com/asp2aspx.htm

this is a expensive solution but it works