如何使 CMS 与现有的 ASP.NET 应用程序在 IIS 中和平相处？
注意：我最初在 ServerFault 上发布了此内容，但我根本没有收到任何回复。因为看起来我有望在那里获得风滚草徽章，所以我想我也可以在这里尝试一下。
我们现有的公共网站由 ASP.NET 页面的大杂烩组成，其中大部分是静态内容，以及一些设置为虚拟目录的真实 Web 应用程序。我们现在正在考虑安装 Umbraco，这要求您将其安装在网站的根目录下。
由于 CMS 位于网站的根部，我假设在 Umbraco 下运行现有页面和 Web 应用程序是一个坏主意（由于它执行 URL 重写并继承 web.config 设置等）那么如何在我们过渡到 CMS 期间以及完成之后，我们是否能让一切和平共处？
到目前为止，我唯一的想法是将 CMS 和应用程序设置为单独的网站，然后使用某种 URL 重写/反向代理来使所有内容正确解析：
* www.example.com would keep resolving to our old homepage
* www.example.com/dept1 would keep resolving to the old dept1 page
* www.example.com/dept2 would resolve to the new dept2 page on the CMS
* www.example.com/app would resolve to an existing web application
Note: I originally posted this on ServerFault, but I haven't gotten any responses at all. Since it looks like I'm on track to get the Tumbleweed badge over there, I figured I would try here also.
Our existing public website consists of a mish-mash of asp.net pages with mostly static content and some real web applications that are set up as virtual directories. We're now looking at installing Umbraco, which requires that you install it at the root of the website.
Since the CMS would be at the root of the website, I'm assuming it's a bad idea to run our existing pages and web applications underneath Umbraco (due to the URL rewriting it performs and inheriting web.config settings, etc.) So how do we make everything co-exist peacefully both while we transition to the CMS and after we're finished?
My only idea so far was to set up the CMS and the applications as separate websites and then use some sort of URL rewriting/reverse proxy to make everything resolve correctly:
* www.example.com would keep resolving to our old homepage
* www.example.com/dept1 would keep resolving to the old dept1 page
* www.example.com/dept2 would resolve to the new dept2 page on the CMS
* www.example.com/app would resolve to an existing web application
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我们最终在 IIS 中将 Umbraco 设置为其自己的网站，然后购买了 ISAPI Rewrite，以便我们可以无缝地传递某些 URL 的 CMS 内容。
We ending up setting up Umbraco as it's own website in IIS and then we bought ISAPI Rewrite so that we could seamlessly pass through CMS content for certain URLs.