I know when you set to true ,it will shadow copy the files.But what does shadow copy mean and why we need to shadow copy files?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I know when you set to true ,it will shadow copy the files.But what does shadow copy mean and why we need to shadow copy files?
Shadow copy creates a copy of the assembly you are referencing.
The reason for this is that .Net (more exactly Windows) cannot unload (some) assemblies within a process once loaded. Because of this you could never replace an assembly without shutting down the entire process because the file remains locked by the OS.
However if you have a shadow copy .Net actually uses that to load your classes you can replace the original .dll file and only the shadow copy (that nobody ‘cares’ about) stays locked.
This is especially important in some environments (e.g. a webserver where you obviously don’t want to shut down the entire server just to run a new version of some web-application).