I recently used a virtual machine that included the BizTalk ESB Toolkit. When i tried to start the machine everything worked fine, so i decided to startup some projects.
At the part where i wanted to design an ESB Itinerary i faced the issue that the designer was not showing. At first i suspected that a corrupted registry entry was the cause and was preparing myself for a fresh install untill i noticed something.
The visual studio version link that i used was different than another link i had on the system;’
"C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe"
"C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" /rootSuffix Exp /RANU
As Aaron Marten points out this is related to the new security layer where it should not be required for a visual studio developer to have full access to the machine. In my case this postfix was added due to a earlier installation of the VS.Net CTP or some other not released version. Later on the newer version was installed but the link had remained in the system.
It seems that the itinerary designer requires some additional rights due to access in the filesystem, registry or whatever. In my case i only had to use another link to get the desired itinerary designer….