查看完整的 Asp.Net Web 配置
有没有一个工具可以输出 ASP.Net Web 应用程序的完整配置。显然，您拥有当前级别的 web.config 文件，但这可能是从许多其他 web.config 一直继承到 machine.config。我希望能够从层次结构中一直查看完整的配置。
我问这个问题是因为我们有一个应用程序正在尝试在 SharePoint (2010) IIS (7.5) 网站下运行。当我们创建一个单独的不同 IIS 站点并直接指向物理文件时，我们就可以让它工作。然而，当我们在 SharePoint (2010) 站点下创建新的虚拟目录/应用程序时，它就会失败（事件日志显示 KernelBase.dll 崩溃）。我们已经检查了 web.config 并添加/删除了各种元素，但它仍然无法正常工作。如果我可以从两个角度捕获同一应用程序的完整配置，这可能有助于我们诊断问题。
谢谢。
Is there a tool out there that can output an ASP.Net web applications's complete configuration. Obviously you have the web.config file at the level you are at, but this is inheriting from possibly numerous other web.configs all the way up to the machine.config. I would like to be able to view the complete configuration from all the way up the hierarchy.
I ask this as we have an application we are trying to get working beneath a SharePoint (2010) IIS (7.5) site. We can get it working when we create a separate distinct IIS site and point directly at the physical files. However when we create a new virtual directory/application beneath a SharePoint (2010) site it just fails (Event log says KernelBase.dll crash). We've gone through the web.config and added/removed various elements but it is still not working. If I could capture the complete configuration of the same application from the 2 perspectives, that might help us diagnose the problem.
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不知道有一种工具（但这并不意味着不存在），但是我们以前也遇到过继承问题。您的基础站点是否运行不同版本的 .net 框架？还要检查列出的所有 web.config 库及其版本。如果站点中的任何内容需要使用较新的版本（例如 4.0）运行，则可能会导致问题，反之亦然。
尝试在父应用程序中围绕 system.web 配置部分添加此部分：
<位置路径=“。”继承InChildApplications =“假”>
<系统.web>
..
<代码>
但请注意，这会影响其他应用程序。如果这解决了问题，但对您的其他应用程序产生了负面影响，那么您可能需要将父级删除的设置复制到需要它的子应用程序中。
I'm not aware of a tool (doesn't mean one doesn't exist though) however we've had inheritance issues before as well. Is your base site running a different version of the .net framework? also check all web.config libraries listed and their versions. If anything requires in the site runs with a newer version say 4.0, it could cause issues or vice versa.
Try adding in the parent app this section around system.web config section:
<location path="." inheritInChildApplications="false">
<system.web>
..
</system.web>
</location>
however note that this will affect other applications. If this fixes it, but negatively affects your other apps then you may need to duplicate the parents removed settings into the child apps that need it.