使用 Web 表单的 .Net 4.0 路由
我正在尝试使用 URL 路由将站点从经典 asp 转换为 .Net 4.0。我已将 IIS6 设置为通过 .Net .dll 通配符映射所有传入请求。到目前为止，一切似乎都进展顺利。旧的 URL 结构非常统一，因此编写 MapPageRoutes 变得轻而易举。因此，我很担心这项任务会变得多么容易。我是 url 路由的新手，所以我想知道这里是否有任何陷阱或需要注意的事项？
I'm trying to convert a site from classic asp to .Net 4.0 using URL Routing. I've set up IIS6 to wildcard map all incoming requests through the .Net .dll. So far everything seems to be working great. The old URL structure is extremely uniform so writing the MapPageRoutes has been a breeze. So much so, I'm concerned at how easy this task is shaping up to be. I'm new to url routing so I'd just like to know if there are any gotchas or something I need to watch out for here?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您已经走到这一步并且没有任何问题，那么请拍拍自己的背。仅从您的描述来看，我能想到的唯一可能是问题的是 IIS6 通配符映射。如果您有一个 CPU 密集型网站，它可能会变成性能问题，所以要小心。 .Net 4.0 路由也应该可以直接与 IIS6 一起使用。因此，如果您的通配符成为问题，您可能需要查看 这个。
If you've gotten this far and don't have any issues then give yourself a pat on the back. Just judging from your description the only thing I can think of that could be an issue would be the IIS6 wildcard mapping. It can turn into a performance issue if you have a cpu intensive website, so be careful there. .Net 4.0 routing is also supposed to just work right out of the box with IIS6. So if your wildcard becomes an issue you may want to look into this.