5) I really don't get this point. I never deployed to Azure and in my work I have a Windows Server VM with IIS on top of it. All I do is clicking publish in VS and pointing the right website. Where is the complexity in this?
You deploy into your production environment from within the GUI development tools without assurance that what's going into production is in version control and independent of the peculiarities of your personal machine when MSDeploy doesn't have a clear rollback process.
This suggestion is ridiculous. You can right-click Publish from the Visual Studio integration, but at no point are you told about packages or the ability to rollback.
That's what I meant by "clear" ... there is no clear ability to rollback from a VS-initiated MSDeploy.
