clip_image00132222222Local Overview

Curtin University Controls Costs, Streamlines IT, and Improves Education with Cloud Platform

clip_image001422222222Readiness & Resources:

Reading:

  • Windows Azure

Creating your own identity provider for Windows Azure AppFabric Access Control

Windows Azure diagnostics via xml config

Silverlight in the Azure cloud - Part 1

Image Upload and Silverlight Deep Zoom Viewing with Azure

  • SQL Azure

How to Connect to SQL Azure Using ADO.net

Watch:

Case Study:

Tools:

clip_image0011022222222Guidance:

Walkthrough:

Design:

clip_image001622222222 In the news:

General news:

Microsoft:

Windows Azure:

clip_image0011222222222Events:

Local:

Global:

clip_image001822222222Community:

Mailing list for OzAzure

Like Azure?

clip_image00132222222Questions:

This week I'm picking simply a scenario based question:

What the best way to test and debug a local application?

"If your app is simply a website, then you don't need to run the compute emulator to run it. I would setup the site so that it runs on IIS on a specific port, then debug the website project, not the cloud project.

There is a bit more to it than just that however. If you're using development storage then you'll need to start that yourself as it won't automatically be started when you debug the website. If you have a RoleEntryPoint class then you need to be aware that none of that code will be called. Also if you make use of anything in RoleEnvironment (like settings) you'll need to put a wrapper around those items so that they'll still work when not running under the emulation environment (RoleEnvironment.IsAvailable is very useful for detecting this). A setup like this is very useful during development because when you make small changes to CSS of JavaScript you don't need to restart the compute emulator to see your changes"