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.
我正在评估从经典ASP 3.0应用程序到ASP.NET MVC的迁移。我已经将应用程序迁移到WebForms，但是出于多种原因决定尝试使用MVC进行迁移，包括这个应用程序中的代码不是意大利面，而且似乎适合MVC风格的布局。
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.
这种迁移的一个主要限制是它必须是渐进式的，停机时间最短（或最好没有），并且应该可以在迁移过程中继续开发。这意味着经典的ASP代码必须与ASP.NET MVC代码并行运行，甚至可能在同一个IIS应用程序中运行。
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?)
- 防止重新路由影响经典.asp文件的最佳方法是什么？ （忽略它们，HttpHandler，特殊的重新路由规则？）
- 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?
- 在使用ASP.NET MVC时，身份验证，会话和常规代码是否会重复使用常规ASP到WebForms迁移的问题？
Thanks in advance!
提前致谢！
2 个解决方案
#1
2
Only have the answer to 1
只有答案1
routes.IgnoreRoute("{resource}.asp/{*pathInfo}");
Did I get a cookie?
我有饼干吗？
#2
-4
MVC uses .net so file extensions are .aspx. You shouldn't have any trouble at all.
MVC使用.net，因此文件扩展名为.aspx。你根本不应该有任何麻烦。
#1
2
Only have the answer to 1
只有答案1
routes.IgnoreRoute("{resource}.asp/{*pathInfo}");
Did I get a cookie?
我有饼干吗？
#2
-4
MVC uses .net so file extensions are .aspx. You shouldn't have any trouble at all.
MVC使用.net，因此文件扩展名为.aspx。你根本不应该有任何麻烦。