Rick van den Bosch - Blog

Have you notice any side effects/issues after setting shadowCopyBinAssemblies="false" ?

Same problem for a few days....this most definitely helped.  

Thank you!

It seems that fixed my headache right now, thank you very much :)

I too was getting this error constantly and was almost at the point of switching to notepad2 to code in like my good old pre visual studio days. I was using the Cassini server on my laptop and got so fed up decided to install IIS to run the pages through that instead. Once IIS was installed, I tried Cassini some more and have not received that error a single time since. So, just wanted to mention that as a possible fix for this issue for those still seeing it. Worked for me with nicely.

Oh, as an FYI, someone here www.mcse.ms/message2503855.html mentions a side effect of setting the shadowCopyBinAssemblies to false.

Try doing an IISReset.  That seems to work for me.

>Try doing an IISReset

You can also:

Re-start VS

Re-start your computer

Put your finger in the air and whistle

All of these <may> fix the problem, as it is intermittent - one minute the error pops up, you close the browser and try again and the error doesn't pop up.

Adding the entry in web.config fixed the problem. thanks for posting this.

Thanks, worked fine.

I started getting 'access denied' error. Do I need to do something else?

Thank you...

Thanks. it worked for me. even though restarting IIS, VS, browser solves the problem, but its not permament solution. Better to add that little markup shadowCopyBinAssemblies="false" in the web.config file.

I had the same problem, but then realised I had a command prompt open located within the gac_msil\<dll>\<version> folder from when I had done the backup xcopy out of the gac.  

Closing this the update of the dll in the gac worked fine

Andy

Hi,

Just for info this is caused by an important .NET feature - the compiled files (all your module DLLs, all the .cs codebehind classes and the dynamicly created _aspx classes generates from the .aspx files) are not actually executed in the /bin folder

Instead all these binaries are copied to a dynamically created subdirectory deep down in the 2.0 framework folder (same folder if you're using 3.5 as the core ASP.NET engine is the same) and executed here.

This feature is what allows you to update your .aspx files on the fly - without compiling and redeploying your core /bin binaries.

When you do this - all existing request (usres) are served from the /Windows/.NET/2.0 directory while your  /bin files are recompiled and then "shadow copied" into the .NET folder.

Interestingly all the .aspx files are dynamically compiles into classes named [pageclass]_aspx - which of course inherit from the .cs class defined as the codebehind.

This means users can continue to use your site while you are correcting your HTML (thou of course you should never ever do this as it slows the site completely - at least don't ever get caught doing it).

Cleaning up ASP.NET temporary files worked for me

The easy way of avoiding the problem is to perform a Solution->Clean before running the web app.  This always fixs the problem.

Thanks,it worked for me.

Tried all of the above but still no luck ... any other tip that might solve this problem.

thanks for your research, saved me [end tasking] asp_wp.exe every time i build and [F5]

brilliant!

Cannot create/shadow copy 'your assembly info here' when that file already exists

add this code in Web.config in System.web section

<hostingEnvironment shadowCopyBinAssemblies="false" />

is working Thanks