Tuesday, 22 May 2007

Cannot create/shadow copy when that file already exists

The .Net Framework has a feature called Shadow Copy. Shadow copy is enabled on every appdomain created by ASP.NET by default. By default assemblies loaded will be copied to a shadow copy cache directory, and will be used from that location. Why does ASP.Net do this? So the original file is not locked and can be modified. An interesting error I have ran into intermittently when running ASP.Net apps with the debugger is 'Cannot create/shadow copy when that file already exists' I'm still not sure why this happens only on occasion, as I can often clean my solution, then reload a web app and it will work fine then. But if you are getting it frequently enough for it to affect your work, you can add the following to your app's web.config or the master .Net web.config:
   <hostingEnvironment shadowCopyBinAssemblies="false" />


Mukesh said...

I have the same problem

Anonymous said...