A better Web Deploy authoring experience
Make the Web Deploy authoring and packaging experience more powerful. Add editing support into VS to add custom deployment steps and control all the providers that WD supports.
There is a lot of power in Web Deploy that most developers don't use since they rely in the default build steps and don't want to go through the hassle of authoring the Web Deploy packages manually.
Ideally I want to right-click my project, choose "Add custom Web Deploy step" and do things like setup IIS bindings, create a registry key, register a certificate, set file permissions etc.
Then when I build the "package" MSBuild target (or /p:DeployOnBuild=true;DeployTarget=Package) these settings will be used.
Sigurdur G. Gunnarsson
shared this idea
Thanks for the idea. I agree that this would be pretty cool.
I’m not sure if you are aware but in VS2012 when you create a publish profile we save the file as .pubxml under Properties\PublishProfiles.
I was thinking that we could have a .pubxml editor/designer. So the idea would be that if you wanted to fine tune your publish/package process you could edit the .pubxml file in that way.
My only hesitation is that I’m not sure how many people would be interested in this. If we get a good amount of votes on this item we can do a deeper investigation on this.
2 comments
-
Luca Morelli commented
create a registry key, register certificate are server operations: if i understood well these are not covered by .pubxml itself, but may be nice to have the opportunity to execute a custom powershell script in the server
-
Sigurdur G. Gunnarsson
commented
I have not used .pubxml files no, so I have two questions:
1) Can they be used to only create the package, not deploy it anywhere?
2) As part of an automated build process (using /p:DeployOnBuild=true;DeployTarget=Package), how can I choose which .pubxml file to use?
