The tale of how the PowerShell CmdLets got installed with Azure SDK 1.4

Posted by Enrique Lima on Geeks with Blogs See other posts from Geeks with Blogs or by Enrique Lima
Published on Sat, 12 Mar 2011 02:43:55 GMT Indexed on 2011/03/12 8:10 UTC
Read the original article Hit count: 243

Filed under:

I installed the Azure SDK 1.4 while rebuilding my laptop and ran the installation for the Windows Azure Service Management PowerShell CmdLets.

Kicked off the installation script for the WASM PowerShell CmdLets by locating the path to which WASM PowerShell CmdLets was deployed to.

SNAGHTML18c4a6

Double clicked the startHere command. It will then open the WASM installation dialog.

SNAGHTML19d29a

Click Next.

SNAGHTML1a4105

Click Next.

SNAGHTML1ab1e1

Notice the red x next to the Azure SDK 1.3, the problem is I have SDK 1.4

Here is the workaround, I go back to the location of the deployed WASM sources.

SNAGHTML1c01c4

Go into the setup path, then scripts>dependencies>check.

SNAGHTML1cd835

Now, locate the CheckAzureSDK.ps1 file, and right-click, then edit.

This is the content in the ps1 file, it check for the specific version of the Azure SDK, in this case, it is looking for version 1.3.11133.0038.

image

We need for it to check for version 1.4.20227.1419

image

Now, save your ps1 file, go back to the open WASM install dialog, and click rescan.

SNAGHTML20d3f1

This time it should pass, then click next.

SNAGHTML2158e9

A Command prompt window will appear, click any key.

SNAGHTML21edf7

This completes the installation, click Close.

SNAGHTML226cb7

© Geeks with Blogs or respective owner