-
You need to structure your schema differently. First you need a root node and then drag each existing element under this root. Root - delimited hex 0x0A postfix BC.Biz.Xsd.Cus.I_810903_20080801 - delimited hex 0x09 postfix EOF tag=EOF (no delimiters)
-
Macros can only be used on send ports, where they use message /environmental properties to construct a filename. On a receive location you can only use a file mask like MyFile_*.txt
-
The issue lies with your xpath expression. it is currently looking for a root node called SendDataResult, with no namespace. Your xpath expression should be something like: "string(/*[local-name()='SendDataResponse']/*[local-name()='SendDataResult'])"
-
The class used is Microsoft.BizTalk.Deployment.Binding.BindingInfo in the Microsoft.BizTalk.Deployment.dll library. But a big gotcha with binding files is they are wrappers for configuration data specified in other assemblies. i.e each pipeline component and adapter has its own configuration classes. These classes serialize their config data into the binding file.
-
A simple method would be to use C# scripting functoids: One page one have a C# scripting functoid with this code: string globalVariable = null; public string SetVariable(string param) { globalVariable = param; return param; } Then on page 2 add a C# scripting functoid public string GetVariablePage2() { return globalVariable; } And on page 3 public string GetVariablePage3() { return globalVariable; }
-
We nned to know what the property name is, but intellisense should help with this. M1(PropertyName) = value;
-
There is no way to perform a one to many mapping in the receive port. The pipeline uses the message type of the incoming message and will execute the first map whose source schema matches the incoming message type. This allows a many to one mapping and is the basis of the normalisation pattern i.e. map into an internal schema that has a processed in an orchestration the result of which can be mapped into many different output schemas if required. The output mapping can be accomplished using multiple
-
I don't believe you can use WIX by itself to create a BizTalk package. Have you looked at the Biztalk Deployment Framework: http://biztalkdeployment.codeplex.com/
-
You do not need to have a send port in your orchestration. What do you do in your expression shape?
-
The orchestration will block on the method call to your assembly i.e. will not progress until the method call has completed. Does your method initiate another thread and then return?