RJ Dudley

Received this bit of cool news yesterday:

Dear Customer,

We are pleased to announce that starting on June 28, 2010, we will be increasing the size limit of a SQL Azure Business Edition database from 10 GB to 50 GB and that of a SQL Azure Web Edition database from 1 GB to 5 GB.  Please note that if you elect to increase your existing databases to take advantage of these new sizes, there are additional charges.  Please refer to our offer comparison table for more details by offer on our pricing.

Thank you for your business and your continued interest in the Windows Azure platform.

Windows Azure Platform Team

Join the Pgh.NET User Group on June 9 as Vijay Koneru gives an overview of programming Silverlight applications using the Azure Cloud Services API. Also, Craig Oaks will provide an introduction to using Silverlight with ArcGIS.

Date:     Tuesday, June 9
Time:     5:30 - 8 p.m.    
Venue:    Microsoft Offices, 30 Isabella Street, 15212

Register: http://webportal.pghtech.org/Events/CalendarEventsListView.aspx

My biddy Shaun's latest ASP Alliance article has been published, and details some of our experiences of working with Azure.

Azure Basics - Say 'Hello' to the Cloud

Shaun shows how to start developing a Windows Azure-based website and shows the steps to deploy that website to the cloud. This is a pretty basic example to help get someone past the basic hurdles of developing for Azure.

Preparing for today's Pittsburgh Code Camp talk was challenge, since we were stringing together a lot of things that are half baked.  On of the issues we had was with log messages (RoleManager.WriteToLog) not appearing in the development fabric UI.  Lindsay had the same problem when she was demoing Azure Services for MSDN Across America a couple weeks ago.

I would see the log messages once, then no messages for subsequent runs.  I finally figured out that if you shut down and exit the Development Fabric UI, then let it restart with the next run, your messages will log.  Unfortunately, you'll need to do this each time you want to examine logged output.