-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Closed
Labels
area-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsfeature-iisIncludes: IIS, ANCMIncludes: IIS, ANCM
Description
Describe the bug
After installing ASP.NET Core 3.0 Runtime and Hosting bundle I've noticed that there are 2 identical IIS schema files installed under C:\Windows\System32\inetsrv\config\schema.
To Reproduce
Steps to reproduce the behavior:
- Install the hosting bundle on a clean box
- observe the contents of C:\Windows\System32\inetsrv\config\schema
- compare the 2 aspnetcore files and see that they are identical
Steps to reproduce the IIS manager confusion
- Install the .NET Core 2 hosting bundle on a clean box
- observe the contents of C:\Windows\System32\inetsrv\config\schema
- iisreset
- Verify that IIS manager can edit the aspnetcore settings
- install .NET Core 3 preview bundle as above
- iisreset
- observe that stdOutLogFile is missing from the config
- observe that there are 2 schema files with the same settings
Expected behavior
There is no need to have 2 files for the exact same schema.
This seems to be a bug with a minimal impact if you only install .NET Core 3 bundle, but can cause some confusion if there were previous versions.
When installed on top of the .NET Core 2.1 version IIS manager actually got confused and didn't show the standard stdOutLogFile option in Configuration editor.
Uninstalling all versions and re-installing .NET Core 3.0 preview bundle fixed the issue but it now has 2 identical files.
Metadata
Metadata
Assignees
Labels
area-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsfeature-iisIncludes: IIS, ANCMIncludes: IIS, ANCM