You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
often there is a clear demarcation of responsibilities between developer and IIS administrator. It would be very useful if the one liner 'Use any of several methods to move the app to the hosting system, such as manual copy, Xcopy, Robocopy, or PowerShell.' was expanded upon so developer understands what needs to be produced from Visual Studio for distribution to the IIS admins and what IIS admins should expect and what they need to do with it.
What needs to be produced from Visual Studio for distribution to the IIS admins
I can improve this bit by adding an additional link to the Directory Structure topic (there's one just a bit earlier in the topic). The Directory Structure topic needs a few minor touch-ups as well.
What IIS admins should expect and what they need to do with it
Beyond the content of Host on IIS, ANCM reference, Directory Structure, Troubleshooting, and the Common Errors topic, additional coverage for IIS admins is probably beyond the scope of this doc set. I can cross-link these topics to the IIS doc set better to help IIS admins.
The text was updated successfully, but these errors were encountered:
From @cnicco ...
RE: Hosting on IIS
https://docs.microsoft.com/aspnet/core/host-and-deploy/iis
host-and-deploy/iis/index.md
Thanks @cnicco for the comment! 🚀
What needs to be produced from Visual Studio for distribution to the IIS admins
I can improve this bit by adding an additional link to the Directory Structure topic (there's one just a bit earlier in the topic). The Directory Structure topic needs a few minor touch-ups as well.
What IIS admins should expect and what they need to do with it
Beyond the content of Host on IIS, ANCM reference, Directory Structure, Troubleshooting, and the Common Errors topic, additional coverage for IIS admins is probably beyond the scope of this doc set. I can cross-link these topics to the IIS doc set better to help IIS admins.
The text was updated successfully, but these errors were encountered: