逐步将经典 ASP 3.0 迁移到 ASP.NET MVC
我正在评估从经典 ASP 3.0 应用程序到 ASP.NET MVC 的迁移。我已经将应用程序迁移到 WebForms,但出于多种原因决定尝试使用 MVC 进行此迁移,其中包括此应用程序中的代码不是意大利面条,并且似乎适合 MVC 样式布局。
这种迁移的一个主要限制是它必须是渐进的,并且停机时间最少(或最好没有),并且在迁移过程中应该可以继续开发。这意味着经典 ASP 代码必须与 ASP.NET MVC 代码并行运行,甚至可能在同一个 IIS 应用程序中运行。
因此,我有几个相关问题:
- 防止重新路由影响经典 .asp 文件的最佳方法是什么? (忽略它们,HttpHandler,特殊的重新路由规则?)
- 人们在类似的场景/迁移中是否遇到过任何特殊的非明显问题?
- 使用 ASP.NET MVC 时,在常规 ASP 到 WebForms 迁移中通常会出现的身份验证、会话和一般代码重用问题是否有什么不同?
提前致谢!
I'm evaluating a migration from a classic ASP 3.0 application to ASP.NET MVC. I've already migrated applications to WebForms, but have decided to try MVC for this migration for a number of reasons, including the fact the code in this application is NOT spaghetti and seems to lend itself to an MVC style layout.
One major constraint on this migration is that it has to be gradual with minimal (or preferably no) downtime, and it should be possible to continue development while the migration is in progress. This means that the classic ASP code has to run side-by-side with the ASP.NET MVC code, probably even in the same IIS application.
So, I have a couple of related questions:
- What's the best way to prevent rerouting from affecting classic .asp files? (Ignore them, HttpHandler, special reroute rules?)
- Are there any special non-obvious issues that people have encountered in similar scenarios/migrations?
- Are the authentication, session and general code re-use issues that generally crop up in regular ASP to WebForms migrations any different when working with ASP.NET MVC?
Thanks in advance!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
只有 1
我得到了 cookie 吗?
Only have the answer to 1
Did I get a cookie?
MVC 使用 .net,因此文件扩展名为 .aspx。你不应该有任何麻烦。
MVC uses .net so file extensions are .aspx. You shouldn't have any trouble at all.