Split CloudDeploy into separate soln by task about connectthedots HOT 3 CLOSED

Also rename to something like AzurePrep.

from connectthedots.

CloudDeploy does two distinct things - create NS, EH, SA assets, and create the web.config file for later publishing the website. Suggest splitting into two, so they can be run independently. Roughly speaking, suggest:

The first ('AzurePrep') present a UI to allow the user to enter Azure credentials, and the proposed name for the namespace. It should then log on to Azure, programmatically get the publishsettings file, display any options to the user and let them choose the subscription, and then create the assets.

The second ('CreateWebConfig') should present a UI to allow the user to enter Azure credentials, get anything it needs, then create the web.config file in a location of the user's choice.

from connectthedots.

Would also be good to have updated error checking for choosing a name for the namespace, including violating requirements, whether already exists, etc.

from connectthedots.