Disclaimer: All postings are provided "AS IS" with no warranties, and confer no rights. This weblog does not represent the thoughts, intentions, plans or strategies of Microsoft. Because a weblog is intended to provide a semi-permanent point-in-time snapshot, you should not consider out of date posts to reflect current thoughts and opinions.
Kevin Williamson has a great post on the overall flow of things from the point of publishing of your package up on the Windows Azure Developer Portal to Run().
These are good things to know as many times you need to inject steps, tasks, context at various stages of your service instance’s lifetime.
Windows Azure Role Architecture - Windows Azure - Troubleshooting & Debugging - Site Home - MSDN Blogs
So, as one of the OneTAP leads for Windows Azure focusing on the BizSpark folks, I run into many questions regarding HOWTO and in areas of Auto-Scaling, provisioning, authentication.
The folks at Full Scale 180 (http://www.fullscale180.com) have created a nice sample application that demonstrates the following:
CloudNinja - Windows Azure Multi-tenant Sample - Home
This is a very nice addition and will make development across the various WebSSO protocols that much easier.
Announcing the WIF Extension for SAML 2.0 Protocol Community Technology Preview! - Claims-Based Identity Blog - Site Home - MSDN Blogs
With the NetFx 4.0 platform update, the WF state machine is back…
Microsoft .NET Framework 4 Platform Update 1 - The .NET Endpoint - Site Home - MSDN Blogs
Reflector has been invaluable over the years. I’m torn about the idea it’s become a paid for tool, and by all means folks should be compensated for great work. Not sure where Lutz is in the cash flow.
But, the ICSharpCode guys have released ILSpy at www.ILSpy.com (http://wiki.sharpdevelop.net/ilspy.ashx)
Right now the limitation is it’s NetFx 4.0+. So, keep that unfortunately self-updating version of Reflector around. I still may pay, but it’s good to know there’s competition.