Seeking opinions on asp2aspx (Netcoole software) - Converting asp to aspx

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a fairly in-depth website that uses traditional ASP, which needs to
be converted to dotnet.

I had been looking for some info on migrating the code (VBScript in the asp
pages) to dotnet and came across the ASP2ASPX conversion tool.

Has anyone used this? What were the results? How much after-the-fact
"fixing" do you have to do?

Just wondering if the cost ($300) is worth it, versus having to transfer a
bunch of ASP pages (probably 60,000+ lines of code) into .ASPX pages.

SC
 
I have a fairly in-depth website that uses traditional ASP, which needs to
be converted to dotnet.

I had been looking for some info on migrating the code (VBScript in the asp
pages) to dotnet and came across the ASP2ASPX conversion tool.

Has anyone used this? What were the results? How much after-the-fact
"fixing" do you have to do?

Just wondering if the cost ($300) is worth it, versus having to transfer a
bunch of ASP pages (probably 60,000+ lines of code) into .ASPX pages.
Click to expand...

Bought it and used it. It is well worth while if you are trying to do a
minimal port of asp to aspx. There are several little syntax differences
between asp and aspx which this tool will take care of for you.

The kind of conversion that this tool is good for is the kind where you have
a large, finished, working, tested asp application, and you want to add
asp.net functionality incremently to it. After the conversion you will
still want to rewrite your pages using the asp.net web forms model.

David
 
I can't comment on the tool, but generally speaking, during the conversion,
most people like to take advantage of the new features in .NET such as user
controls, inheritance, server side event handlers, etc.This means that a
straight up conversion isn't enough - it's typically redesigning the
structure to be more efficient, more maintainable, and with less code. I
know that there is a price to pay in the extra delay to redesign the site,
but it may very well be worth it.
 
<<I can't comment on the tool, but generally speaking, during the
conversion, most people like to take advantage of the new features in .NET
such as user controls, inheritance, server side event handlers, etc.This
means that a straight up conversion isn't enough - it's typically
redesigning the structure to be more efficient, more maintainable, and with
less code. I know that there is a price to pay in the extra delay to
redesign the site, but it may very well be worth it.>>

That is exactly what's been running thru my mind as well.

On one hand, it'd be nice to have the bells & whistles that dotnet would
gain by rewriting the application. On the other hand, it is a working
website, and our user base (not exactly the most computer savvy bunch in the
world) is familiar with the way things work on that system, and a direct
translation would probably soften the transition to the new system.

We currently are running both dotnet and traditional asp on the same
production website.

Another consideration is the weeks & months it'd take me to rewrite the
website in dotnet, versus what this might bring us. Right now, we've got
tons of sql reports that are output in the old part of our system, and need
a way to get them into the new system. As it is now, the daily stuff I have
to maintain or produce new makes it difficult to get the time to devote to a
rewrite of something that isn't exactly broken, and is fairly heavily used.

SC
 
Back
Top