ASP.NET hostingEnvironment / shadowCopyBinAssemblies [英] ASP.NET hostingEnvironment / shadowCopyBinAssemblies

问题描述

今天，我在stumpled在 shadowCopyBinAssemblies 选项，在 hostingEnvironment 标记。

Today I stumpled upon the shadowCopyBinAssemblies option in the hostingEnvironment tag.

Appearently这个属性是一个的web.config （System.Web程序）配置布尔选项指示是否在Bin目录中的应用程序的组件影像复制到该应用程序的ASP.NET临时文件目录

Appearently this attribute it is a web.config (system.web) configuration Boolean option indicating whether the assemblies of an application in the Bin directory are shadow copied to the application's ASP.NET Temporary Files directory.

<hostingEnvironment shadowCopyBinAssemblies="false" />

一个同事<一个href=\"http://dotnetsoldier.blogspot.com/2008/09/cannot-create-shadow-copy-visual-studio_1635.html\">had启用此设置因为头（只）他的开发机器上他频频得到了ASP.NET错误在Web浏览器：

A colleague had to enable this setting because (only) on his development machine he frequently got that ASP.NET error in the web browser:

 Cannot create shadow copy assembly file dll when that file already exists.

编译Visual Studio 2008中一个特定的web项目和openining的页面。

compiling a specific web project in Visual Studio 2008 and openining a page.

所以现在我的问题：我可以preserve此设置的在生产环境中或可能损害其性能和/或创建其他问题

So now my question: can I preserve this setting in a production environment or could it harm performance and/or create other issues?

的谢谢！的

推荐答案

我得到这个错误不时，通常做的清理解决方案之后的重建解决方案需要关心这个问题。如果这适用于您的同事，那么就没有必要与设置（特别是在生产中）来播放。

I get this error from time to time, and usually doing Clean Solution followed by Rebuild Solution takes care of the problem. If this works for your colleague, then there's no need to play with the setting (especially in production).

这篇关于ASP.NET hostingEnvironment / shadowCopyBinAssemblies的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！