Cannot create/shadow copy 'VariousFileName' when that file already exists.

Posted by pzolja on 3/2/2007 at 9:27 AM

It usually happens when I write custom controls or use controls that I write. Restarting the web server (the one that comes with VS or IIS) or cleaning the solution fixes the problem. I wish I wouldn't have to resort to doing this though...

Posted by Fabrice Marguerie on 5/14/2007 at 9:45 AM

Could you reopen this bug, please? It's closed as "won't fix", but without explanation. This bug is real, appeared with VS SP1 and should be fixed.

Posted by jwrummell on 6/18/2007 at 9:17 AM

I agree with nbenin, reopen please!

Posted by lchilds on 7/3/2007 at 12:55 PM

This error happens too often and forces you to end your debug session. I agree that it needs to be resolved or at least explained.

Posted by Seshu Palachulla on 7/5/2007 at 2:59 PM

Ok, I just had the problem with it a few moments ago and I was surprised to this message for the first time.My Enviroment is Visual Studio 2005 on Windows Server 2003.

Ok The error came when I deleted or uninstalled an assembly from the GAC and then rebuild the new dll and tried to add it.

My work around is

1. Go to Command Prompt
2. Navigate to C:\Windows\Assembly\GAC_MSIL"
3. What is the Name of the your assembly? A folder by that assembly name exists. delete that folder
4. Try installing the Assembly once again.

It should work and you would not get the message a copy of file already exists. When you have installed successfully the folder with your assembly name that you just deleted will be recreated.

Hope it is useful

Thanks
Seshu Palachulla

Posted by SLADR on 7/19/2007 at 3:04 AM

I also agree with nbenin, reopen it

I got this error in my release - version on "Windows 2003 Server", IIS6, .NET 2.0!

There is no visual studio installed on this machine!

Posted by mjmcmahon on 7/23/2007 at 9:22 PM

I've been experiencing this problem today as well while trying to debug and test a web service via an NUnit test class.

Environment: Visual Studio 2005 Version 8.0.50727.762
OS: Windows XP SP2

Posted by geordiepaul on 10/10/2007 at 4:22 AM

This is by far and away the most annoying Visual Studio "Bug". Everyone gets it but it would appear Microsoft won't acknowledge this and fix it!

Why won't you fix it?

Posted by roboffer on 10/10/2007 at 4:31 AM

This needs to be reopened and fixed. C'mon Bill get Visual Studio installed.

Posted by This_handle_has_been_reserved_by_another on 12/31/2007 at 9:26 AM

Yes, please re-open. Or at the very least, explain why you won't fix it.

Posted by mausch on 8/19/2008 at 7:03 AM

This still happens to me with VS2008, win2k3

Posted by Stijn V on 9/24/2008 at 2:35 AM

It has come pretty far. Developers are now begging MS to at least acknowledge their errors. MS says hey, its fixed. If you want you can complain on this webform. Talk to the hand.

Posted by CarlosTheJackal on 1/21/2009 at 8:12 AM

Agreed, my whole team suffers with this problem. Seems to happen only with Enterprise Library assemblies, including Unity.

Posted by goggles8 on 8/18/2009 at 4:24 PM

I google this error and get over 50,000 search results and yet not fix??????
I am seriously considering moving to another platform

Posted by BradUffner on 1/19/2007 at 9:37 AM

add <hostingEnvironment shadowCopyBinAssemblies="false" /> to the <system.web> section of your web.config file.

Posted by salgo60 on 2/13/2007 at 2:51 AM

Restart Cassini when you get the problem

Posted by syrnux on 2/16/2007 at 6:30 AM

If you get the error, stop the debugger, right click the solution and "clean solution". Hit F5 to restart debugger. This is really annoying as it has >50% fail rate for me and you would think that there *should not be a manual option to CLEAN SOLUTION!* This $1200 POS application should clean it for you automatically!

Posted by cavehop on 6/11/2007 at 11:03 AM

Here's another workaround that may be more appealing to some, courtesy of Gary Farr (http://blogs.claritycon.com/blogs/gary_farr/archive/2007/03/09/2888.aspx).

Add the following to your pre-build events:
IF EXIST $(TargetPath).LOCKED (del $(TargetPath).LOCKED) ELSE (IF EXIST $(TargetPath) (move $(TargetPath) $(TargetPath).LOCKED))

Posted by 3foottall on 6/18/2007 at 9:43 AM

A workaround that does the job for me is instead of using "Build" use "Build Solution"

Posted by kbertin on 9/12/2007 at 5:58 AM

after a successful build, i count to ten, then i refresh my webform.

Posted by bgab on 9/18/2008 at 6:51 AM

I have found that by re-registering ASP.NET against IIS the problem "goes away" - I haven't had the problem since. You will need to run the following on the command line: "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i". This more than likely won't work for everyone - it's a complex problem.

Posted by Stijn V on 9/24/2008 at 2:31 AM

I know a good workaround:

Uninstall vs2008, sell it, and download Eclipse for free.

Posted by alancnet on 12/9/2008 at 8:48 PM

Works for me:

if exist "$(TargetPath).locked" del "$(TargetPath).locked"
if exist "$(TargetPath)" if not exist "$(TargetPath).locked" move "$(TargetPath)" "$(TargetPath).locked"

Posted by zooooe on 3/5/2009 at 8:32 PM

restart VS.

Posted by clothesofsand on 9/23/2009 at 5:44 AM

When Cleaning the solution, a few warnings were issued about files that could not be deleted. These files had their read-only property set. After setting the property of these files to read/write, the problem was solved.