I had a big weekend, and I think its blog worthy. I won the BizSpark Azure Camp pitching competition.

http://blogs.msdn.com/ausdev/archive/2010/04/12/bizspark-camp-australia.aspx

http://www.microsoft.com/australia/presspass/post/Microsoft-launches-Windows-Azure-in-Australia

Neat huh?

This is one of those ‘duh’ things that you feel silly for spending 20 minutes on. Okay okay. 30 minutes…okay 45 minutes.

With the ESB toolkit the Itinerary Designer doesn’t live in a BizTalk project, it goes in a C# project. If you click on a BizTalk project and “Add –> New Itinerary” you don’t get a error, but the normal BizTalk add item dialog appears. Stupidly, the add item dialog has “Add New Itinerary” in the title bar, but there is no itinerary to choose. For 20 minutes it looked like the ESB Toolkit Visual Studio addin’s were corrupted or not installed correctly. Okay, 45 minutes…sheesh.

This is the thread that wised me up.

http://social.msdn.microsoft.com/Forums/en/biztalkesb/thread/050cc72d-0313-4ac7-ade5-d4da5cc3f014

I was just running the ESBConfigurationTool.exe to install the ESB Toolkit and I got the following exception.

“Could not load file or assembly ‘System.Management.Automation’ etc”

The configuration tool expects that Powershell is installed and it turns out on this particular server it wasn’t. Through the server manager I added PowerShell under “Features” and I was back in business.