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.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?Sigurdur G. Gunnarsson shared this idea ·
141 votesunder review · 7 comments · General ASP.NET » General ASP.NET · Flag idea as inappropriate… · Admin →
602 votesunder review · 9 comments · General ASP.NET » Web Deployment · Flag idea as inappropriate… · Admin →
16 votesSigurdur G. Gunnarsson commented
I would like the see auto-populated OPTIONS out of the box, and don't see why people would not like it?