Address file-locking issue in IIS #27395
Labels
area-networking
Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions
design-proposal
This issue represents a design proposal for a different issue, linked in the description
Theme: meeting developer expectations
Summary
When someone wants to deploy an app to IIS, they currently require either an external tool or to know that they need to drop the file
app_offline
to the directory to shutdown the app. If someone tries to deploy the app without doing this, files will be locked as they are currently being used.This is a regression from .NET Framework, which used shadowcopying. This is a proposal to add some sort of shadow copying implementation to ANCM, giving customers an option to not have to worry about locked files.
People with more context
@jkotalik, @davidfowl, @Tratcher
Motivation and goals
In scope
A list of major scenarios, perhaps in priority order.
Out of scope
Scenarios you explicitly want to exclude.
Risks / unknowns
Examples
Give brief examples of possible developer experiences (e.g., code they would write).
Don't be deeply concerned with how it would be implemented yet. Your examples could even be from other technology stacks.
The text was updated successfully, but these errors were encountered: