Which means I should be able to delete my bin folder and I should not be able to delete shadow copy folder. Please correct me if I am wrong but I would expect that IIS would lock files in shadow copy folder and it should watch files path which is configured on iis website. Especially after reading ShadowCopyDoesNotLockFiles test case.

after deleting shadowcopy folder application was still working and responding on requests (folder at that time was not regenerated.

when apppool is running I was able to delete entire shadowcopy folder.

when apppool is running I was unable to delete bin folder in my project root.

shadow copy gets created correctly and it's contents is updated on apppool restarts.

for website which on iis points to main project directoryĪnd on both configurations bahaviour was the same.

I've tested if behaviour for shadowcopy is the same for: I've spent some more time to check if I am not doing something wrong. But the problem is that I am still getting the same locking error during build if applicaiton is still runningĪm I using it wrong? I couldn't find any end to end example how it should work and what is the expected behaviour. I can see in logs that shadow copy kicks in (it created new folder with copy of the whole web project contents). I've installed new hosting bundle and tried to run it with application using net core 3.1. Today I read about that shadowcopy feature and got really excited to try it. Only way to work with that was to use visual studio which is able to stop->deploy->start apppool. And obviously when website was running any try to build website was showing errors about locked files in /bin folder. Since aspnetcoremodulev2 for IIS I am using in proc hosting which points to root directory of my asp.net core application. But from first time I was using dotnet core I was trying to set dev environment to work similar to what I've experienced with old asp.net. Hello I've just used shadow copy feature.

Unlock a dll file