The publish-iis tool will now generate web.config files inside the root of your output, not in the web root (wwwroot).
This means that IIS will now need to be configured to point to the root of your site instead of the web root like it has up-to-now for ASP.NET Core.
Simplified Old Layout
/root
/wwwroot/ <-- IIS physical path
site.css
web.config
myapp.dll
In this case IIS would be configured to use /root/wwwroot as the root of your web application.
Simplified New Layout
/root <-- IIS physical path
/wwwroot/
site.css
myapp.dll
web.config
In this case IIS would be configured to use /root as the root of your web application.
This is the same web.config location and pysical path you would have used in your ASP.NET 4.x applications. Moving the web.config file location to the root of the application enables publishing of muliple applications using Web Deploy.
Your applications static content will still need to go in the web root (wwwroot in these examples). The static files middleware is what serves static content in your application and it will still only serve from the web root regardless of the physical path configured in IIS.
Please use aspnet/IISIntegration#158 for discussion
The
publish-iistool will now generateweb.configfiles inside the root of your output, not in the web root (wwwroot).This means that IIS will now need to be configured to point to the root of your site instead of the web root like it has up-to-now for ASP.NET Core.
Simplified Old Layout
In this case IIS would be configured to use
/root/wwwrootas the root of your web application.Simplified New Layout
In this case IIS would be configured to use
/rootas the root of your web application.This is the same
web.configlocation and pysical path you would have used in your ASP.NET 4.x applications. Moving theweb.configfile location to the root of the application enables publishing of muliple applications using Web Deploy.Your applications static content will still need to go in the web root (wwwroot in these examples). The static files middleware is what serves static content in your application and it will still only serve from the web root regardless of the physical path configured in IIS.
Please use aspnet/IISIntegration#158 for discussion