Ok, so here's another thing that would make you say, "this is the last time I'll ever use Biztalk again"
If you have VS.NET 2003 and Biztalk installed on your machine, and then you install VS.NET 2005 beta 2, the Biztalk Web services publishing tool will fail to generate web services. This is really annoying, it means that I can't have Biztalk and VS.NET 2005 installed on the same machine. I faced this problem before, and the solution was to uninstall VS.NET 2005 and reinstall VS.NET 2003 and Biztalk.
Yesterday I faced the same problem, but there's no way I'm gonna uninstall VS.NET 2005 again, so I had to find another solution.
Biztalk uses Visual Studio.NET to generate the web services solution, so what's probably happening is that when Biztalk calls VS.NET, the 2005 version gets called instead of the 2003 version. I also remembered that when I run the devenv.exe from the Run window, VS.NET 2005 starts, so for sure there's a setting some where that tells windows where is this exe file located. And the first place I looked in is, of course, the registry.
I found this key HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Windows\CurrentVersion\App Paths\devenv.exe. It had this value
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe, which is pointing to the VS.NET 2005 executable. So I changed it to point to VS.NET 2003
C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.exe
And also my manager, Tarek Bohsali, once told me that I need to change the following key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\VisualStudio.Solution\CLSID to this value {246C57AE-40DD-4d6b-9E8D-B0F5757BB2A8}
Changing these two keys solved the problem, and now I'm able to publish my orchestrations as web services.