Skip to main content

Configuring a Development Sandbox for the Azure CTP

I'm getting up to speed on Azure and the other cloud SDKs and need to configure an environment for development, demos and learning. My experiences...

First off, if you've read my blog, you know I haven't installed non-productivity software on my core OS for years. Further, I don't get the warm and fuzzies installing CTP software on my core OS. I also love the recoverability and start-over-from-a-checkpoint features of virtualization. Virtual PC (VPC) houses all my development, demo and learning sandbox instances. So, let's start off with a VPC instance. For this to work well, ideally, you need a good 4GB of memory. Further to the ideal, you're running x64 so as to have access to the full 4GB of memory.

ACQUIRE AN AZURE SERVICES DEVELOPER KEY

To develop against Azure and/or .Net Services and SQL Services, you need an invitation code. Oooh, very exclusive. Pretty people to the front of the line! You can start the process here. If you run into problems, check this post here or the forums here. All invitations and registrations are managed out of Microsoft Connect.

Azure requires either Vista or Windows Server 2008. Fortunately, Microsoft provides a trial VPC download of Windows Server 2008.

CONFIGURE WINDOWS SERVER 2008 VPC

  • Make sure you have Virtual PC 2007 with SP1 installed
  • Download the Virtual Hard Drive (VHD) file and expand
  • Within the Virtual PC Console, select: New >> Create a virtual machine >> provide a name and location >> Windows Server 2008 >> Adjust the RAM to at least 2GB if not 2.5GB (2560MB) >> An existing virtual hard disk (browse out to the VHD file you downloaded above and expanded) >> Finish
  • Fire up the VPC instance and log in (credentials are on the download page)
  • (TIP: If you need to flip between the window frame and Full Screen, it's Right-ALT + Enter)
  • Suggestion: Right-mouse on the desktop, Properties, Screen Saver: None.
  • Start >> Administrative Tools >> Server Manager (may already be up when you log in)
  • Click on Add a Feature
    • Within .NET Framework 3.0 Features, select the .NET Framework 3.0, (and within that...) select WCF Activation, (and within that...) select HTTP Activation and finally but optionally Windows PowerShell
    • Install
  • Click on Add a Role
    • Select Web Server (IIS)
    • Click Add Required Features
    • Under Role Services, select ASP.NET (click Add Required Role Services if prompted)
    • Install
  • Create a share to your core OS
    • Within the window frame of the VPC instance, select File...Install or update...additions
    • Run Setup.exe and follow the instructions to install the additions. Restart if prompted.
    • Within the window frame of the VPC instance, select Edit...Settings
    • Select Shared Folders. Click Share Folder...
    • We're setting up a share to all this software we're about to install which you've downloaded (or will). Typically, I have an Installs directory housing all my software installation files.
  • Firewall: I'm not 100% sure this is required but I enabled port 1433 through the firewall for SQL Server. Instructions.

INSTALL THE SOFTWARE

Download or copy and then install all this software into the folder on your core OS which we just shared to the VPC. I typically just install from the share. This conserves space and prevents the virtual hard drive from expanding unnecessarily.

Comments

Popular posts from this blog

TFS Error | The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.

Posting this one for the search engines. If you ever receive the exception "The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.", more than likely, your drive space is at 0 on your TFS application tier box.

I encountered this at a client recently. The root cause was that IIS logs had filled up the OS drive (C:\). I switched IIS logging to the applications drive (D:\) which cleaned up the OS drive and resolved the issue.

Detailed message:


TF53010: The following error has occurred in a Team Foundation component or extension:


Date (UTC): 6/7/2011 4:18:53 PM

Machine: TFSATBOX

Application Domain: /LM/W3SVC/8080/ROOT/tfs-1-129519118182628600

Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727

Service Host: 7ecfbd77-b386-4d75-b038-b05474782696 (DefaultCollection)

Process Details:

Process Name: w3wp

Process Id: 3676

Thread Id: 5752

Ac…

Verified by Visa: Everything We Tell Folks to Avoid

Phishing is defined by F-Secure as: "Fraudulent e-mail or website claiming to be legitimate seeking indentifiable information. Phishing is an attempt to steal your personal data."When I recently attempted an online purchase from WalMart using my VISA card, being a security wanta-be, I immediately thought phishing when redirected to verifiedbyvisa.com and saw this dialog:

Seriously, these folks have to be kidding. You're asking for my personal data during a transaction and claim that's its a service "...at no additional cost." Wow! Thanks...but absolutely not, you jokers. As a malicious thief, I can go a long way with this data.

This is exactly the type of experience which aids malfeasance and the folks trying to steal personal data / identities. How long have we been working to educate folks to avoid providing this type of data under these type of circumstances? Years. And we're just now starting to turn the corner.

VISA, get rid of this! When folks submi…

Windows 10 Creator's Update and Office Conflicts

Recently, Microsoft pushed the "Creators Update" out to Windows 10. It was available in April but it seems to have been force-pushed in the past 2 days. On my mother-in-law's computer, Creator's caused Excel to render a "Bad Image" message when attempting to start declaring "MSVCP140.dll is either not designed to run on Windows or it contains an error". I attempted the SFC and DISM repairs as advised on Tom's site to no avail. When I attempted an Office repair, Office disappeared completely. At this point, I definitely started to panic.

Fortunately, I noticed a pending reboot due to an install/update. Allowing Windows to install that update and rebooting twice brought Excel and Office back to life. I did have to re-register the software but all is well now. If you encounter this issue, stop what you're doing and install/restart Windows. Anecdotally, I've since hear of many folks encountering similar issues.