IIS Step fails instead of converting an existing physical directory to Web Application or Virtual Directory

[michaelnoonan]

The existing Step Templates for IIS Web Application and Virtual Directory will attempt to convert an existing physical directory to a Web Application/Virtual Directory, but the new IIS Step fails without attempting the conversion. This prevents people from using Custom Installation Directory targeting a physical path matching the virtual path in IIS. Several customers have been naturally using this approach due to their previous experience managing IIS Virtual Directories etc.

https://library.octopusdeploy.com/step-template/actiontemplate-iis-application-create
https://library.octopusdeploy.com/step-template/actiontemplate-iis-virtual-directory-create

We should make the new step more consistent with the existing Step Templates instead of blindly failing without attempting the conversion.

Source: http://help.octopusdeploy.com/discussions/problems/48239-iis-deploy-setting-up-both-virtual-and-phisycal-path-possible-bug

Source: http://help.octopusdeploy.com/discussions/problems/47940-problem-creating-new-iis-application-with-new-step-type-deploy-an-iis-web-site

[octoreleasebot]

Release Note: Converting an existing physical directory to either a Virtual Directory or Web Application in IIS now works, just like it used to in the old Step Templates

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.