Cannot create/shadow copy when that file already exists

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:






Charnsak Srisawatsakul (Joyce)

Product Programme IT Team.


Loan and Related System.

Bangkok Bank Public Company Limited.



Confidentiality and Disclaimer

This e-mail and any attachments hereto (the E-mail) may contain information which is confidential and/or proprietary and transmitted for the sole use of the recipient(s) named above and for the intended purpose only. If you are not the intended recipient of the E-mail, you are hereby notified that any review, copy, retransmission, distribution, or use of the E-mail in any manner for any purpose is strictly prohibited and please notify the sender, delete the original of the E-mail and destroy all copies immediately. Bangkok Bank accepts no responsibility for any mis-transmission or virus contamination of, or interference with, the E-mail, or for any loss or damage that may be incurred as a result of the use of any information contained in the E-mail.    

Leave a Reply