We managed to get our web site “Created” but not deployed. This means we moved to the end of page 2 in our training guide. We talked about the training guide here.
Here’s the web site we’ve “Created.” What they call “Deploying” the web site is actually putting files out there that support your audience’s use case. They make the appropriate analogy to IIS where you right click and select “New” to create the web site and then add and edit the files in the site’s virtual root folder to support the target application.
The problem is that there doesn’t seem to be a simple file structure you can use to just put files out there. We have to use an FTP utility or, inside Visual Studio, we can just deploy our project out there.
We’ll get to that in a bit but first, the authors take us in a slightly different direction. Next, they want us to do the same thing in PowerShell. No prob, we’re PowerShell experts, which is good because the authors presume you’re a PowerShell expert and provide virtually no context for making PowerShell work in Azure other than to point us to a link at MSDN here. And, while that is a pretty good references for the Azure PoSh commandlets, the real Azure PoSh setup is covered here.
The steps are:
- Download the Installer – Mine was called WindowsAzurePowerShell.3f.3f.3fnew.exe.
- Run the Installer – Mine ran the Windows Web Platform Installer 5.0 and allowed me to install Microsoft Azure PowerShell 0.9.
- Accept the license terms.
- Watch the progress bars.
- Click Finish.
- Add all the options and click Install.
- Get a gun and shoot yourself
The install wizard will try to install the Visual Studio tools to make your life easier and they are encumbered by a number of prerequisites so you get this:
So this will all be different based on your Visual Studio install but I went into Control Panel | Programs and Features when I right clicked on Visual Studio and selected Change, then Modify. I added the data tools and let it run. And then my anti-virus started to object so I clicked through a bunch of warnings and the install timed out so I started it again and it said it was already installed so I rebooted and tried a third time and got a similar error about some other VS feature and on and on.
I can only say that I read through and executed the tasks lists on the Azure.Microsoft site here. And they get into the weeds pretty deep when it comes to version 0.9.x and version 1.3.0 and the Resource Manager modules and the Service Manager modules and on and on. Plus there’s this PowerShell Gallery which they don’t tell you is here and, apparently, it’s another install unless you’re on Win10.
The main objective here is to be able to run PowerShell and, in PowerShell run:
and get back something that includes these:
C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ResourceManager\AzureResourceManager C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ServiceManagement C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\Storage
And, of course, the folders where these module reside may differ.
That’s all there is to it. And we can move on to page 3.