Available for download here, you’ll find the first step in taking a-Expense to Windows Azure. Highlights of this release are:
#1 is straight forward thanks to SQL Azure relatively high fidelity with SQL Server.
For #2, we used the providers included in the Windows Azure training kit (with a few modifications/simplifications). The main challenge here is to initially migrate the data from the “on premises” SQL Server to Azure storage.
#3 is relatively simple by using WIF. The main changes are in the UserRepository class where instead of calling the (Simulated)LDAPProvider, we simply inspect the claims collection in the current principal:
#4 requires “claims enabling” a-Expense. Look inside the web.config for all extra config sections added by WIF:
It also requires a valid “Issuer” of claims. We have included a “Simulated” Issuer that creates the token we need. You’ll find this as part of the solution:
And of course in the application configuration:
We are also using a WIF configuration that is “web farm friendly”. Check the global.asax file for details. Here’s a note on the Claims Guide hat talks about it:
#5 is also rather simple. Because we are using EntLib blocks, we just defined the right trace listener:
The complement to this is a new class in the project (WebRole) where all the initialization happens:
#6 is just a bunch of PowerShell scripts. We are using the Azure CmdLets built by Ryan’s team which are great! These hide us all the underlying details of the Windows Azure Management API.
Some lessons learned