We have a few BizTalk 2009 projects going on at the moment and are running into some issues. The latest is the that when deploying a project containing an orchestration from Visual Studio 2008 you see an exception similar to:
“xlang/s engine event log entry: FileLoadException exception occurred while the XLANG/s runtime enlisted a service.
Error message:Could not load file or assembly ‘EnvDTE, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)”
The problem here seems to be that the orchestration was deleted from BizTalk (usually through the Administration Console), but the Redeploy property of the BizTalk project in Visual Studio is set to True. Once you set the Redeploy property of the project to False it will deploy fine.
Eliasen has posted about the other issues that we have been noticing, mostly between BizTalk 2009 and Visual Studio 2008:
Some of these we have reported to Microsoft already so I’ll post back when that gets some traction.
Update 17 November 2009: There is a hotfix coming up that fixes most if not all of these issues, keep tuned and I will update this post when it is released (either separately or as a service pack for BizTalk 2009).