236 votesRaymond commented
I'd prefer to have a more robust solution based on the IIS step (but without it being tied to deploying a package, of course). Why don't you create a separate step to just create an IIS site and add that to your standard steps? Or even better: Remove the requirement of deploying a package from the IIS step altogether? You already have a standard step to deploy a package, so why also tie that requirement it to the IIS step? That would make a lot of sense to me and make the whole process a lot more flexible and suitable for enterprise usage.
3 votesRaymond shared this idea ·