Did I miss something or is the answer to this question harder to track down than it should be? As documented in the 'BizTalk Server 2006 Installation Guide - Multiserver.doc', Document Explorer 2005 is a dependency for the BizTalk 2006 documentation. So the operations team on my current engagement asks me where it comes from... and I respond that that is a good question and that I'll have an answer for them in a couple of minutes. After a few tens of minutes I've inferred that it is part of the Visual ......
I recently put together a VPC of the BizTalk 2006 RTM on Windows Server 2003. I followed the installation guide and I had no problems during the installation or configuration. A few days later, during an impromptu sales demo I was asked to show how you would set up an orchestration to call a web service. I didn’t have a local web service so I fired up VS 2005 to create one – only to discover that I couldn’t find the Web Services project template. Why? Because it is only installed ......
I’m working on several projects and I have to switch between BizTalk 2004 and BizTalk 2006. Since they aren’t supported in a ‘side-by-side’ manner I’ve kept BizTalk 2004 on my base machine and run BizTalk 2006 in Virtual PC. Sometimes I need to have a lot of applications running on my machine so I don’t always have enough memory to have BizTalk 2004 running and also run the BizTalk 2006 VPC image so I’ve create two batch scripts to start and stop BizTalk ......
I’ve come across a situation a couple of times in the past where I could not see certain (custom) properties in a Receive shapes’s filter list. In my cases, this appeared to happen when: I was attempting to use a property from a property schema that is in a different assembly from the schema that contains the node that you have promoted and The schema that contains the promoted property’s underlying value is the base type for the message the Receive shape will receive and I set ......