What tools, practices, or documentation have you used in your conversion process that you would recommend to others?
相关问题
- Carriage Return (ASCII chr 13) is missing from tex
- How to store image outside of the website's ro
- 'System.Threading.ThreadAbortException' in
- Request.PathInfo issues and XSS attacks
- How to dynamically load partial view Via jquery aj
相关文章
- asp.net HiddenField控件扩展问题
- asp.net HiddenField控件扩展问题
- Asp.Net网站无法写入错误日志,测试站点可以,正是站点不行
- asp.net mvc 重定向到vue hash字符串丢失
- FormsAuthenticationTicket expires too soon
- “Dynamic operations can only be performed in homog
- What is the best way to create a lock from a web a
- Add to htmlAttributes for custom ActionLink helper
You could try Microsoft's
ASP to ASP.NET 1.x Migration Assistant
I guess it's better than nothing.
one is a scripting language and other compiled so the overall paradigm itself is completely different and I am really skeptical that there would be anyway to convert / migrate your app from classic asp to asp.net, if you intend to use asp.net the way its meant to be.
There is a quick and dirty way to convert from ASP to ASP.Net since ASP.Net supports inline coding that was used in ASP Classic. However, you wouldn't be taking full advantage of ASP.Net with that approach.
The bad news is there's no easy way to convert from ASP Classic to ASP.Net the "right" way. They are such different technologies there's no streamlined conversion process.
We've converted a few ASP classic apps to .net, and are in the process of converting another.
What we did was first to split them into two groups - ones that we would convert completely, before replacing the old with the new, and then the ones we could convert incrementally.
For that second group, it was useful to build some header and sidebar controls for the app that also held some of the more programmy parts - security, navigation and such, and then use an iframe for holding the ASP classic stuff, in the areas we haven't gotten to converting yet.
It's been pretty painless, as we can pull out the old, and insert the new on our own schedule, rather than having to get the entire massive app rewritten before moving forward. It's also helped us be able to tailor the changes and new features to our customers' needs.