Using a new folder for each deployment in IIS causes asp.net core cookies to be invalidated

Hi,

When we deploy a new version of our app we like to deploy to a new folder each time.

e.g.

C:\mysite\1.0.0\web

then

C:\mysite\1.0.1\web

The final part of the deployment process updates the IIS site to set its physical_path to be the path to the app.

Switching the physical_path is triggering the asp.net core cookies to be invalidated, forcing all users to login again.

We do not see this behavior if there is an IISRESET, the application pool recycles or if the server restarts. It is only occurring when we change the physical_path on deployment.

Are there some settings / configuration we can use to stop this from happening? I am guessing that changing the physical_path is changing the unique id used by the data protection layer.

Is deploying to the same folder over and over the only way we can stop the invalidation of cookies from happening?

Thanks