ASP.NET hostingEnvironment / shadowCopyBinAssemblies

Today I attacked the shadowCopyBinAssemblies parameter in the hostingEnvironment tag .. p>

Initially, this attribute is a web.config (system.web) Boolean configuration, indicating whether the application nodes in the Bin directory will be shadow copies in the application. Directory of temporary ASP.NET files.

<hostingEnvironment shadowCopyBinAssemblies="false" /> 

A colleague had to enable this option because (only) on his development machine he often received this ASP.NET error in a web browser:

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

Compiling a specific web project in Visual Studio 2008 and opening a page.

So now my question is: can I save this setting in a production environment or can it hurt performance and / or create other problems?

Thank!

+6
web-config assemblies
Nov 11 '08 at 15:08
source share
1 answer

I get this error from time to time and usually execute a Clean solution followed by Reconstruction> . If this works for your colleague, then there is no need to play with tuning (especially in production).

+3
Nov 11 '08 at 15:35
source share



All Articles