Is there a particular reason for locking access to the zip-files? Automated deployment fails when files cannot be overwritten or deleted! We should not have to stop the site in IIS to deploy code!?
Currnetly we have build step for releasing .zip file. Waiting for some EPi answer..
There's no reason for locking, it's just the default behaviour when opening a file stream and since the data is read on demand it's kept open.
This is not a desired behaviour, and there's a bug reported for it.
Bug solved! http://world.episerver.com/Documentation/Release-Notes/ReleaseNote/?releaseNoteId=114349
Now I can remove my very long waiting step...
Great, this slipped through my filter somehow :)