Check it out @ Cloudy in Seattle.  This is a great timesaver if you’re building your own deveopment environment or just installing on a clean box.

To start, run Visual Studio as an administrator.

File –> New Project

We’ll begin by selecting the File –> New Project menu item in Visual Studio 2008. 

Once the New Project dialog box is brought up, select the Cloud Service Project Type on the left hand side of the dialog.  On the right hand side of the dialog, choose Web Cloud Service. 

We’ll name the project “HelloCloud” and click the OK button to create the project.

Newly Created Azure Solution

When the solution loads, two projects are created as within it.  The HelloCloud_WebRole is a standard ASP.NET project.  It is where we will be building our website.  The HelloCloud project is a Cloud Service project.  This project references the HelloCould_WebRole project and also contains a configuration file for our solution. 

Creating the Default Page

Creating our Default page will be minimal.  We will add a label to the page, which will display our Hello Cloud text.

Add the following code inside the form tag.

<div>
    <asp:Label ID="Label1" runat="server" Text="Hello Cloud" />
</div>

Testing the Page

Press the F5 key to start the application in Debug mode.  The ASP.NET project will compile as normal.  However, since there is a Cloud Service project in the solution, it will use the development fabric to load the application.  Finally, the page will load and display our “Hello Cloud” message.

If you look at the task bar, you will notice a new icon.  This icon is for the development fabric, which simulates the Azure runtime environment.  It is used for building and testing Azure services locally on your machine.

Wrap-up

In this post, we looked at building a simple service.   In later installments, we’ll cover debugging and logging, deployment, and the Azure dashboard.

• 11 hands-on labs
• 18 demo scripts
• 9 presentations (including speaker notes)

The latest Azure Tools for Microsoft Visual Studio & SDK is the March 2009 CTP Release.

This post will walk you through the steps to setup a Facebook development machine.  I develop using a VPC image.  You can find steps to setup your own VPC development image here (part I, part II, part III).  If you are not using a VPC image, skip any steps related to VPC setup.

One caveat before we get started.  This requires you to have administrator access to your WIFI access point.  This will not be possible to do at Starbucks or your favorite local WIFI spot.

Setup Your VPC Networking Adapter

If you’re developing using a VPC, you will need to make sure you are using one of the Network Adapters built into your machine.  Select your VPC Image in the VPC console and click Settings.  Select Networking.  Pick one of the Network Adapters.  If you’re going to be connecting using a wireless connection, select the wireless adapter.  Likewise, if you’re going to connect by wire, pick the Ethernet connection. 

Do not pick Local Only, Shared Networking (NAT), or Not Connected.  These will not allow proper pass-through of network calls.   At this point, you will need to restart your virtual machine.

Get Your IP Address

You will need your IP address for several steps in our walk through.  The easiest way to obtain your IP address is to visit whatsmyip.org.  This site will detect your IP address and display it on the screen.  Write the address down.  You will need it later.

Update Your Hosts File

The next step is to update your hosts file.  This will create a pass through between the incoming request on your IP address and your local image.  Browse to your hosts file.  It can be found at windows\system32\etc\ in WinXP machines.  For Vista, the hosts file is found at windows\system32\drivers\etc.  Open the file using Notepad.  Add a new line and enter 127.0.0.1 at the start of the new line.  Tab over and enter your IP address.  In the image below, your IP address would replace 999.999.999.999.  Save the file.

Update Your Routing Tables

Now that we have your IP address and the hosts file updated, it’s time to update the routing table in your Wifi/Router.  You will need Administrator access to your Wifi Access Point for this step.  Log into your router  and browse to the Routing Tables.   This can have many different names depending on the brand of your Wifi/Router.  For my Belkin Router, it’s call Virtual Servers.  Setup will be similar to the image below.  Set the inbound port to port 80.  Set the IP address to the local address of your development machine.  This can be found somewhere in your router.  It is not the IP address we got in step 2.

Once your entry is setup similar to entry #4 above, apply the changes.

Open a Hole in the Firewall

Next we need to open up a hole in our firewall to allow traffic through on port 80.  For this walk through, we’re going to assume the use of Windows Firewall.   If you’re not using Windows Firewall, configuration on your firewall should be similar.  Open Windows Firewall and click Change Settings.  Select the Exceptions tab.  Click the Add Port button.  Give the open port a name, enter 80 for the port to open, and leave TCP selected.  Click OK. 

Create Your Site

Now it’s time to write some code.  For this example, we’ll create a new website.  File -> New Website -> ASP.NET Website.  Be sure to save the site outside of your documents folder.  This will save you the headaches of dealing with permissions and messing with the site ACLs.   To make this as simple as possible, we’re going to delete everything from the Default.aspx page except the @Page declaration.  We’ll then add the following code to the page

<h2>Debug Test Site</h2>

Now you should only have the original @Page declaration and the line of code above.  Save the Page.

Update Facebook to Post to Your Site 

Browse to the Facebook Developer’s Site.  Select your application.  Click on the Edit Settings link.  Select the Canvas tab.  Update the Canvas Callback URL with your IP Address from step 2.  In the image below, you would replace 999.999.999.999 with your IP address.   If your test site’s location is at the localhost root, be sure to remove the testsite addition in the Canvas Callback URL box.

Have Fun and Host Away

 Browsing to your application should yield the following results.

At this point, everything should be setup and you can start hosing and debugging your application.

• Windows Vista w/ SP 1
• Visual Studio 2008 or Visual Web Developer w/ SP 1
• .NET 3.5  Framework w/SP 1 (should be included with the Visual Studio SP1 install)

Once you have these installed, you should have no problems installing the bits.

During the CTP, I get the following:

• Total compute usage: 2000 VM hours (83.3 days running 24/7)
• Cloud storage capacity: 50GB
• Total storage bandwidth: 20GB/day

I plan to start messing around with this over the weekend. I’ll post my experience & thoughts then.

First, we’ll starty by creating a new differencing disk – name it AzureBase.vhd.  Base it off of the XXX_Base.vhd disk image we created on Day 2.

Bring up the Virtual PC Dashboard and point the Azure VMC to use the newly created differencing disk.

Next we need to install our Azure software.

• Install Azure SDK
• Install Toolkit
• Install Training Kit

Mark the AzureBase.vhd disk image read-only.

Create a differencing disk – name it AzureDev.vhd.  Base it off of the AzureBase.vhs disk image.

Bring up the Virtual PC Dashboard and re-Point the Azure VMC to use the newly created differencing disk.

You now have a stable development environment. 

Why did we go through all this trouble to create a development environment?  When the next Azure Beta comes out, you can start at the 2nd disk image and have a full working environment up and running rather quickly.

What about the 3rd differencing disk…that seems kind of pointless.  Well, If you make any changes that break your environment, you only need to recreate the 3rd virtual disk to be back in business.  You could use the Undo feature and work of off the 2nd disk, but then you would lose any progress when you undo the changes.  Plus the differencing disk seems to work slightly faster than using Undo disks.  

Running your Virtual Image for the First Time

Running your new image for the first time will require several additional steps to complete the setup process.

First, check your internet connectivity by browsing to your favorite search engine.  If it doesn’t connect, you’ll need to modify the settings to use Shared Networking (NAT).  This can be done through the VPC interface by selecting your Virtual Machine, clicking Settings, then selecting Networking.

Second, install the Virtual Machine Add-Ons.  Select Install or Update Virtual Machine Addons under the Actions menu.  This will install the VMC Addons, which will greatly improve performance and add some nice touches.  

Further optimizations can be accomplished by following the steps outlined at Andrew Connell’s Site. While these steps are laid out for Windows XP, you can find almost all of the items mentioned with minimal digging in Vista.

Next, install any critical OS updates.  These might be downloading automatically in the background through Windows Update.  However, you may need to verify your copy of Windows is genuine first.

Vista does not install IIS by default, so you will need to set it up.  Follow the steps at Chris Fulstow’s blog to install IIS and configure ASP.NET to run on Vista.

Install VS 2008 or Visual Web Developer onto the image.

Install Office 2007 and any other software you want on the image.

Finally, install service pack 1 for both Visual Studio & .NET 3.5 framework.

Disk Cleanup

Cleaning up your disk will save some space when we compact it. The following are some locations that can have files removed.

• Run Disk cleanup on the C: drive
• Delete any photos, music, video files that may have been installed to your documents folder, including shared documents
• Remove games and any other non-critical OS components you will not need
• Clean out temp folders

Defragment the Disk

Use the Windows defrag utility to defragment the virtual hard disk. This can take over an hour so you don’t need to be constantly monitoring the process.

DisKeeper makes a great tool for defrargging disks. I’ve used it for a few years and highly recommend it.

PreCompact & Compacting the Disk

Merrick Chaffer has an excellent blog post detailing some ways to improve VPC performance.  We’re specifically interested in the Running Precomact and Compacting the .vhd file sections.

Final Steps for the Main Image

Mark the XXX_Base.vhd hard disk image Read-Only. This will prevent any accidental changes to the image. Once we create differencing disks based on this image, any changes to our base image will render our new child images useless. 

Wrap-up

Tomorrow we’ll get into creating differencing disks, installing Azure, and finalizing our development environment.

Download & Install VirtualPC 2007

Get the latest build from Microsoft at the Virtual PC download page.

Virtual PC can be a resource hog. Here are some recommendations for running Virtual PC (VPC).

• Run it on a different hard disk than the one your Host OS is running on, preferably an external Hard Drive.
• Dedicate at least 1GB of memory to the Virtual image, preferably 2GB.  However, make sure to leave enough memory for the Host OS.
• Defrag the hard disk where Virtual PC is installed.

Create a New Virtual Machine / Hard Disk

Start Virtual PC.  Select File -> New Virtual Machine Wizard.  Click Next twice. 

 On the Virtual Machine Name and Location screen, browse to the location where you will be saving your virtual machine.  Name the Virtual Machine (VM) something descriptive.  Since I’m creating a development environment for Windows Azure, I named my VM Azure Dev Environment.  Click Next when you’re happy with the name of your VM.  

Select the OS you will be installing.  In this case, select Windows Vista.  Click Next. 

 Select Adjusting the RAM and adjust to a comfortable level (1024MB if you have 2GB installed on your machine or higher if you have more RAM installed).  Click Next. 

 Select the A New Virtual Hard Disk option. Browse to the location that your Virtual Hard Disk (VHD) will be saved. Name the Virtual Hard Disk XXX_Base.vhd, replacing XXX with the OS that you will be installing.  I will be installing Vista Business, so my VHD is named VistaBusiness_Base.vhd.  Using this naming convention will allow you to keep better track of as your virtual images library grows.  Click Next and then Finished. 

 Your first Virtual Machine image has now been created.  Like any new computer, the virtual hard disk is empty and only contains a basic version of DOS.  We now need to install the Operating System.

Installing the OS

I installed Vista Business Edition for my development environment.  However, Windows Server 2008 will also work with the Azure SDK.  I originally installed Vista Ultimate but encountered problems installing SP1.  Since SP1 is required, I couldn’t install the Azure SDK.  I would be careful if you’re going to install Ultimate since there seems to be issues installing SP1.

 Select CD -> Capture ISO Image from the menu.  Browse to the location of the ISO image containing your Operating System and select it.  Select Action -> Ctl+Alt+Delete from the menu to reset the instance.  The VPC instance should now reboot loading from the ISO and starting the OS installation process.  From this point, follow all of the prompts to install the OS.

Wrap up

This entire exercise shoud take 1-2 hours at most.  Tomorrow I’ll look at steps to take when running the Virtual Image for the first time.

Who am I?  I’m a .NET developer who has been programming professionally for over 9 years, most of which were spent consulting.  I’ve also been known to give a tech talk or two at local user groups and code camps.  I can be found on LinkedIn @ http://www.linkedin.com/in/mattmikulicz.

I used to blog at the midwestcoders.net, but after that site became defunct, I stopped bloggng. I decided to start this blog because I’m really stoked that Cloud Computing has finally made it big time in the Microsoft world with the release of Windows Azure.

There are a ton of buzzwords out there that are very similar or the same (Cloud Computing, SaaS, S+S, SOA, etc.).  Hopefully we can get these straightened out with some good dialog here.

Happy Coding