-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Allow disabling shared configuration check from hosting bundle. #6498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
We'll review this on Thursday's shiproom. |
src/Installers/Windows/AspNetCoreModule-Setup/ANCMV2/aspnetcoremodulev2.wxs
Outdated
Show resolved
Hide resolved
src/Installers/Windows/AspNetCoreModule-Setup/ANCMV1/aspnetcoremodule.wxs
Outdated
Show resolved
Hide resolved
Approved for 2.2.2. |
This was introduced because a majority of the time, when IIS is redirecting configuration, it is pointing to a location where the current user doesn't have write permissions to. When the hosting bundle runs, it will fail to install with no warning/ error (just says it fails to install). There was a few customers complaining about this, and I found that many other IIS installers (UrlRewrite, ARR, etc) had a check for if there was a shared configuration used, and if so fail to install. I added this check to the ANCM msis, but then we realized there was no way to revert this behavior. |
Not sure if this change affects the ANCM packages. If it does, please update the 2.2.2 section of eng/PatchConfig.props: https://github.com/aspnet/Extensions/blob/d8407116d183debaadb801c0cbc41d65927999d6/eng/PatchConfig.props#L7-L10 |
This change will not affect ANCM packages, just the hosting bundle. |
src/Installers/Windows/AspNetCoreModule-Setup/ANCMV1/aspnetcoremodule.wxs
Outdated
Show resolved
Hide resolved
Where are we with this one? Is this ready to check-in? cc @mikaelm12 @dougbu FYI. |
I'd like https://github.com/aspnet/AspNetCore/pull/6498/files/3b658e8022aa260b361d202139cea338e70d399d#diff-f870277bc9a67c26e59bc002457cece7R255 to be approved by @joeloff otherwise LGTM |
FYI I believe @joeloff is OOF today. |
Any updates here? This is the last thing we have for 2.2.2 |
I posted a comment this morning about the uninstall check. Update them to be REMOVE="ALL" |
src/Installers/Windows/AspNetCoreModule-Setup/ANCMV1/aspnetcoremodule.wxs
Show resolved
Hide resolved
src/Installers/Windows/AspNetCoreModule-Setup/ANCMV1/aspnetcoremodule.wxs
Outdated
Show resolved
Hide resolved
src/Installers/Windows/AspNetCoreModule-Setup/ANCMV2/aspnetcoremodulev2.wxs
Outdated
Show resolved
Hide resolved
src/Installers/Windows/AspNetCoreModule-Setup/ANCMV1/aspnetcoremodule.wxs
Show resolved
Hide resolved
Verified the installers work with this change. |
Issue: #4451
Description
When installing the 2.2 Windows Hosting Bundle, today, we block the use of shared applicationHost.config redirection. This was a change made in the time period between 2.2-preview3 and 2.2. However, some customers relied on this behavior when installing the hosting bundle to update a shared configuration file on the same machine. More importantly, there was no way to disable the check in the new hosting bundle.
The fix is to allow users to specify the parameter "OPT_NO_SHARED_CONFIG_CHECK" to disable the shared configuration check.
Usage:
Regression?
Regression from 2.1 hosting bundle.
Risk
Very low. Default scenario are still the same and this only skips a check for shared configuration.