Software Engineering, Project Management, and Effectiveness
While ramping for Windows Azure, we created a quick set of steps to get other team members quickly started with Azure. The goal is tight – get Azure running on your local box and be able to explore and run the Azure SDK samples.
Installing the Azure SDK and the Visual Studio Tools for Azure Here’s a quick set of steps to install the VS tools for Azure and Azure SDK:
Installing the Azure SDK Samples You need to unpack the samples:
Installing the Additional Azure SDK Samples The additional samples include a sample ASP.NET provider for Azure Table Storage. Our team is using this to test ASP.NET Forms Authentication with Azure Table Storage.
Additional Resources Here are some key places to visit:
My Related Posts
8. Run Visual Studio as Administrator *hangs head in shame*
Feels like we're stepping backwards, not forwards on secure development efforts.
I agree and I'm poking around and asking folks some questions.
Any more insights to share?
The thread on Azure involves one of the moderators in the MSDN forum (http://social.msdn.microsoft.com/Forums/en-US/windowsazure/thread/592af192-9a22-4741-b048-6dac65453283/) might give you some information. Saad Ladki from the IIS team suggested that it might not be a result of IIS configuration. I'm hearing a lot of people pointing fingers in other directions. All I want to know is how we can get away from a bad decision that flies in the face of the immutable laws of security administration.
Another similar move was made by the Windows Identity Foundation team which require you to run as admin. They could just have easily selectively elevated or used a broker service to do their ceritifcate generation (rather than having the dev run as admin all the time).
Keep leading the horse to the water.
You have no idea how thirsty the horse is :)