All posts by : The Arch Hackers BizTalk Blog

1 of 48 | BAM Deployment Issue - I discovered a weird problem recently when deploying a BAM definition spreadsheet using the bm.exe program.Basically, I was getting multiple message boxes containing fn_GetString in the title, plus some other blank message boxes until finally the process ended. It looked pretty terminal!The problem turned out to be that on my machine the locale was set to English (United Kingdom) and it looks like the BAM deployment process doesn't like it. The message boxes look like they come from Excel so I guess the BAM Excel spreadsheet macro code is to blame.Changing the locale to English (United States) solved the issue and the bm.exe program was able to export the BAM definition XML successfully fro......

2 of 48 | Delivery Notification Doesn't Appear with Specify Now Binding - Now, I don't pretend to understand this, so if someone can enlighten me, I would appreciate it :)I have a web port type defined in orchestration to a OneWay web service. When I create a port based on the web port type and I select Specify Now in the port configuration, then the Delivery Notification property doesn't appear. If I go into the port properties window and change the binding to Specify Later, the Delivery Notification property appears! Change the binding back, and it disappears again! Eh?My guess is that the delivery notification property is implicitly set when using the SOAP adapter (which is the default using a web port type and specifying the binding in the orchestration),......

3 of 48 | DNJ Interview with Solidsoft CTO Andy James - Ok, ok, so he's my boss ;-) Still, it's a good article about BizTalk and SOA from someone who's been about, if you know what I mean ;-)DNJ Interview Link...

4 of 48 | Fed up of deploying BTS assemblies the 'standard' way? - Well, this is a little tip about deploying a BizTalk assembly quickly and easily without having to unbind, undeploy, redeploy, rebind and all that wonderful stuff.If you recompile a BizTalk assembly that does not affect the current bindings then all you need to do is the following: Open a view onto the GAC by clicking Start->Run and then typing assembly Compile BizTalk assembly Drag and drop the compiled assembly from the bin\Development folder (we're developing, right?) into the assembly view window Restart BizTalk NT service from BizTalk Administration snap-in, Services snap-in or the command line using net stop It really is as simple as that!...

5 of 48 | Multiple Activate Receives and Returning Soap Faults Oddity - Imagine a scenario where you have an orchestration exposed as a web service that has two public ports. Each port accepts a message of the same type, but one port is used to send new messages, and the other is used to send update messages. The port type for the port has an access modifier of public, is a request-response port type, plus has a Fault message defined in addition to the request and response messages.In the orchestration, you create a listen shape and then add two activatable receives - one on each branch with one pointing to the request message of the new port, and one to the request message of the update port. So far so good.At this point you're going to want to create a cou......

6 of 48 | One-Way Web Methods - I made quite a cool little discovery the other day with OneWay web methods in ASP.NET. When I hooked the web service up to my orchestration, I discovered that BizTalk had actually taken the OneWay interaction style into account and only offered a request message type, rather than both a request and response message type. Many people probably know this already, but I found this to be really cool! How many times have I hooked up a web service with an orchestration and ignored the response because the method does not return any value?! More times than I care to remember......

7 of 48 | Returning SOAP Faults from an Orchestration Published as a Web Service - I was asked the question recently: how can I return a SOAP fault from a web service call if the orchestration that has been published has failed?Well, this is seemingly a lot easier than you would think. A request-response port type in orchestration allows multiple Fault Messages to be defined. These fault messages can be based on any message type (for example, System.String) and are returned to the web service in the same manner as returning a response to a web service, that is, via a send shape to the appropriate fault message on the operation defined on the port type.If you were to take a look at the port type definition in the orchestration view tab in VS.NET, then you'll see the variou......

8 of 48 | Using a Map with Large Messages - I was intrigued the other day about how maps were behaving in BizTalk Server 2004 with regard to potential memory problems. BizTalk Server 2004 gives us great large message support through streaming messages into the message box. However, what if we specify a map in the Receive port, or indeed anywhere in BizTalk (Orchestration or Send Port)?Well, BizTalk implements maps as XSLT stylesheets, and the way I understand it, the code uses the XslTransform class to perform the transformation and will load the input message into the DOM. This will require a significant memory footprint if the message is large!This is often overlooked and is worth pointing out......

9 of 48 | WSE Adapter for BizTalk Server 2004 Beta Program - Ok, it looks like Scott Woodgate has released details about the WSE Adapter for BizTalk beta program over on his blog here.The WSE Adapter has a dependency on the WSE 2.0 release that has just recently been made available on the MSDN site....

10 of 48 | BAM Deployment Issue - I discovered a weird problem recently when deploying a BAM definition spreadsheet using the bm.exe program.Basically, I was getting multiple message boxes containing fn_GetString in the title, plus some other blank message boxes until finally the process ended. It looked pretty terminal!The problem turned out to be that on my machine the locale was set to English (United Kingdom) and it looks like the BAM deployment process doesn't like it. The message boxes look like they come from Excel so I guess the BAM Excel spreadsheet macro code is to blame.Changing the locale to English (United States) solved the issue and the bm.exe program was able to export the BAM definition XML successfully fro......

11 of 48 | BizTalk and SOA - So, it's been a while since I've blogged. Life has been hectic and I'm currently spreading my time between two projects so blog time has been in short supply, even though my blog-to-do list is growing! Anyway, so what is this post all about? It's about where BizTalk fits architecturally within the new "hot" world of Service Oriented Architectures. BizTalk Server, as we know, is a middleware product that enables integration between LOB applications and systems in an EAI scenario and trading partners in a B2B scenario. As part of this broad area of responsibility BizTalk is able to execute business processes that implement complex integration or workflow scenarios, transform data fr......

12 of 48 | BTS Guys Understand SOA and Contract First - Aaron Skonnard has put up a good post about why BTS developers understand SOA and contract first. This is a hot topic at Solidsoft Towers and James and Duncan certainly have championed this at work for some time.I was talking with James the other day about the ASHX HTTP handler that bypasses all of the unnecessary XML->Object and Object->XML deserialisation and serialisation that goes on. We agreed that as a lightweight 'web service' for BTS running at the core of a SOA architecture it is essential as it reduces the evil of latency that BTS can introduce (due to its primary task of ensuring messages are durable which means trips to SQL Server that could be avoided in a request-respo......

13 of 48 | Cool XSD Validation Function for Orchestration - As I promised in an earlier post, here's a cool XSD validation function that can be called from within orchestration. Just add to a library - I tend to put it into a BizTalk Utilities library full of useful little functions that complement orchestration (most of which should be provided by the orchestration engine, but that's a rant for another day!).public static void ValidateDocument( XmlDocument businessDocument, string schemaStrongName ){  // Constants  const int PARTS_IN_SCHEMA_STRONG_NAME = 2;  const int PART_CLASS_NAME = 0;  const int PART_QUALIFIED_ASSEMBLY_NAME = 1;  // Parse schema strong name  string[] assemblyNameParts ......

14 of 48 | DateTime Serialization in BizTalk - Possible Bug? - On a recent project, I came across an interesting issue with assigning the current date and time to a promoted property in a Message Assignment shape. The problem highlighted itself in our Audit database where we were auditing process state changes. The submission date of each audited record appeared to be 1 hour ahead than the current local time (based on GMT with Daylight Savings Time in effect - meaning we are currently +1 to UTC). Our scenario involves writing an audit record from the web site that is initiating the process, then each subsequent audit is performed at various steps within a BizTalk orchestration. Each audit record contains some meta data extracted from the en......

15 of 48 | Delivery Notification Doesn't Appear with Specify Now Binding - Now, I don't pretend to understand this, so if someone can enlighten me, I would appreciate it :)I have a web port type defined in orchestration to a OneWay web service. When I create a port based on the web port type and I select Specify Now in the port configuration, then the Delivery Notification property doesn't appear. If I go into the port properties window and change the binding to Specify Later, the Delivery Notification property appears! Change the binding back, and it disappears again! Eh?My guess is that the delivery notification property is implicitly set when using the SOAP adapter (which is the default using a web port type and specifying the binding in the orchestration),......

16 of 48 | DNJ Interview with Solidsoft CTO Andy James - Ok, ok, so he's my boss ;-) Still, it's a good article about BizTalk and SOA from someone who's been about, if you know what I mean ;-)DNJ Interview Link...

17 of 48 | Fed up of deploying BTS assemblies the 'standard' way? - Well, this is a little tip about deploying a BizTalk assembly quickly and easily without having to unbind, undeploy, redeploy, rebind and all that wonderful stuff.If you recompile a BizTalk assembly that does not affect the current bindings then all you need to do is the following: Open a view onto the GAC by clicking Start->Run and then typing assembly Compile BizTalk assembly Drag and drop the compiled assembly from the bin\Development folder (we're developing, right?) into the assembly view window Restart BizTalk NT service from BizTalk Administration snap-in, Services snap-in or the command line using net stop It really is as simple as that!...

18 of 48 | Multiple Activate Receives and Returning Soap Faults Oddity - Imagine a scenario where you have an orchestration exposed as a web service that has two public ports. Each port accepts a message of the same type, but one port is used to send new messages, and the other is used to send update messages. The port type for the port has an access modifier of public, is a request-response port type, plus has a Fault message defined in addition to the request and response messages.In the orchestration, you create a listen shape and then add two activatable receives - one on each branch with one pointing to the request message of the new port, and one to the request message of the update port. So far so good.At this point you're going to want to create a cou......

19 of 48 | One-Way Web Methods - I made quite a cool little discovery the other day with OneWay web methods in ASP.NET. When I hooked the web service up to my orchestration, I discovered that BizTalk had actually taken the OneWay interaction style into account and only offered a request message type, rather than both a request and response message type. Many people probably know this already, but I found this to be really cool! How many times have I hooked up a web service with an orchestration and ignored the response because the method does not return any value?! More times than I care to remember......

20 of 48 | Returning SOAP Faults from an Orchestration Published as a Web Service - I was asked the question recently: how can I return a SOAP fault from a web service call if the orchestration that has been published has failed?Well, this is seemingly a lot easier than you would think. A request-response port type in orchestration allows multiple Fault Messages to be defined. These fault messages can be based on any message type (for example, System.String) and are returned to the web service in the same manner as returning a response to a web service, that is, via a send shape to the appropriate fault message on the operation defined on the port type.If you were to take a look at the port type definition in the orchestration view tab in VS.NET, then you'll see the variou......

21 of 48 | Using a Map with Large Messages - I was intrigued the other day about how maps were behaving in BizTalk Server 2004 with regard to potential memory problems. BizTalk Server 2004 gives us great large message support through streaming messages into the message box. However, what if we specify a map in the Receive port, or indeed anywhere in BizTalk (Orchestration or Send Port)?Well, BizTalk implements maps as XSLT stylesheets, and the way I understand it, the code uses the XslTransform class to perform the transformation and will load the input message into the DOM. This will require a significant memory footprint if the message is large!This is often overlooked and is worth pointing out......

22 of 48 | WSE Adapter for BizTalk Server 2004 Beta Program - Ok, it looks like Scott Woodgate has released details about the WSE Adapter for BizTalk beta program over on his blog here.The WSE Adapter has a dependency on the WSE 2.0 release that has just recently been made available on the MSDN site....

23 of 48 | BAM Deployment Issue - I discovered a weird problem recently when deploying a BAM definition spreadsheet using the bm.exe program.Basically, I was getting multiple message boxes containing fn_GetString in the title, plus some other blank message boxes until finally the process ended. It looked pretty terminal!The problem turned out to be that on my machine the locale was set to English (United Kingdom) and it looks like the BAM deployment process doesn't like it. The message boxes look like they come from Excel so I guess the BAM Excel spreadsheet macro code is to blame.Changing the locale to English (United States) solved the issue and the bm.exe program was able to export the BAM definition XML successfully fro......

24 of 48 | BizTalk and SOA - So, it's been a while since I've blogged. Life has been hectic and I'm currently spreading my time between two projects so blog time has been in short supply, even though my blog-to-do list is growing! Anyway, so what is this post all about? It's about where BizTalk fits architecturally within the new "hot" world of Service Oriented Architectures. BizTalk Server, as we know, is a middleware product that enables integration between LOB applications and systems in an EAI scenario and trading partners in a B2B scenario. As part of this broad area of responsibility BizTalk is able to execute business processes that implement complex integration or workflow scenarios, transform data fr......

25 of 48 | BTS Guys Understand SOA and Contract First - Aaron Skonnard has put up a good post about why BTS developers understand SOA and contract first. This is a hot topic at Solidsoft Towers and James and Duncan certainly have championed this at work for some time.I was talking with James the other day about the ASHX HTTP handler that bypasses all of the unnecessary XML->Object and Object->XML deserialisation and serialisation that goes on. We agreed that as a lightweight 'web service' for BTS running at the core of a SOA architecture it is essential as it reduces the evil of latency that BTS can introduce (due to its primary task of ensuring messages are durable which means trips to SQL Server that could be avoided in a request-respo......

26 of 48 | Cool XSD Validation Function for Orchestration - As I promised in an earlier post, here's a cool XSD validation function that can be called from within orchestration. Just add to a library - I tend to put it into a BizTalk Utilities library full of useful little functions that complement orchestration (most of which should be provided by the orchestration engine, but that's a rant for another day!).public static void ValidateDocument( XmlDocument businessDocument, string schemaStrongName ){  // Constants  const int PARTS_IN_SCHEMA_STRONG_NAME = 2;  const int PART_CLASS_NAME = 0;  const int PART_QUALIFIED_ASSEMBLY_NAME = 1;  // Parse schema strong name  string[] assemblyNameParts ......

27 of 48 | DateTime Serialization in BizTalk - Possible Bug? - On a recent project, I came across an interesting issue with assigning the current date and time to a promoted property in a Message Assignment shape. The problem highlighted itself in our Audit database where we were auditing process state changes. The submission date of each audited record appeared to be 1 hour ahead than the current local time (based on GMT with Daylight Savings Time in effect - meaning we are currently +1 to UTC). Our scenario involves writing an audit record from the web site that is initiating the process, then each subsequent audit is performed at various steps within a BizTalk orchestration. Each audit record contains some meta data extracted from the en......

28 of 48 | Delivery Notification Doesn't Appear with Specify Now Binding - Now, I don't pretend to understand this, so if someone can enlighten me, I would appreciate it :)I have a web port type defined in orchestration to a OneWay web service. When I create a port based on the web port type and I select Specify Now in the port configuration, then the Delivery Notification property doesn't appear. If I go into the port properties window and change the binding to Specify Later, the Delivery Notification property appears! Change the binding back, and it disappears again! Eh?My guess is that the delivery notification property is implicitly set when using the SOAP adapter (which is the default using a web port type and specifying the binding in the orchestration),......

29 of 48 | DNJ Interview with Solidsoft CTO Andy James - Ok, ok, so he's my boss ;-) Still, it's a good article about BizTalk and SOA from someone who's been about, if you know what I mean ;-)DNJ Interview Link...

30 of 48 | Fed up of deploying BTS assemblies the 'standard' way? - Well, this is a little tip about deploying a BizTalk assembly quickly and easily without having to unbind, undeploy, redeploy, rebind and all that wonderful stuff.If you recompile a BizTalk assembly that does not affect the current bindings then all you need to do is the following: Open a view onto the GAC by clicking Start->Run and then typing assembly Compile BizTalk assembly Drag and drop the compiled assembly from the bin\Development folder (we're developing, right?) into the assembly view window Restart BizTalk NT service from BizTalk Administration snap-in, Services snap-in or the command line using net stop It really is as simple as that!...

31 of 48 | Multiple Activate Receives and Returning Soap Faults Oddity - Imagine a scenario where you have an orchestration exposed as a web service that has two public ports. Each port accepts a message of the same type, but one port is used to send new messages, and the other is used to send update messages. The port type for the port has an access modifier of public, is a request-response port type, plus has a Fault message defined in addition to the request and response messages.In the orchestration, you create a listen shape and then add two activatable receives - one on each branch with one pointing to the request message of the new port, and one to the request message of the update port. So far so good.At this point you're going to want to create a cou......

32 of 48 | One-Way Web Methods - I made quite a cool little discovery the other day with OneWay web methods in ASP.NET. When I hooked the web service up to my orchestration, I discovered that BizTalk had actually taken the OneWay interaction style into account and only offered a request message type, rather than both a request and response message type. Many people probably know this already, but I found this to be really cool! How many times have I hooked up a web service with an orchestration and ignored the response because the method does not return any value?! More times than I care to remember......

33 of 48 | Returning SOAP Faults from an Orchestration Published as a Web Service - I was asked the question recently: how can I return a SOAP fault from a web service call if the orchestration that has been published has failed?Well, this is seemingly a lot easier than you would think. A request-response port type in orchestration allows multiple Fault Messages to be defined. These fault messages can be based on any message type (for example, System.String) and are returned to the web service in the same manner as returning a response to a web service, that is, via a send shape to the appropriate fault message on the operation defined on the port type.If you were to take a look at the port type definition in the orchestration view tab in VS.NET, then you'll see the variou......

34 of 48 | Using a Map with Large Messages - I was intrigued the other day about how maps were behaving in BizTalk Server 2004 with regard to potential memory problems. BizTalk Server 2004 gives us great large message support through streaming messages into the message box. However, what if we specify a map in the Receive port, or indeed anywhere in BizTalk (Orchestration or Send Port)?Well, BizTalk implements maps as XSLT stylesheets, and the way I understand it, the code uses the XslTransform class to perform the transformation and will load the input message into the DOM. This will require a significant memory footprint if the message is large!This is often overlooked and is worth pointing out......

35 of 48 | WSE Adapter for BizTalk Server 2004 Beta Program - Ok, it looks like Scott Woodgate has released details about the WSE Adapter for BizTalk beta program over on his blog here.The WSE Adapter has a dependency on the WSE 2.0 release that has just recently been made available on the MSDN site....

36 of 48 | BizTalk and SOA - So, it`s been a while since I`ve blogged. Life has been hectic and I`m currently spreading my time between two projects so blog time has been in short supply, even though my blog-to-do list is growing! Anyway, so what is this post all about? It`s about where BizTalk fits architecturally within the new "hot" world of Service Oriented Architectures. BizTalk Server, as we know, is a middleware product that enables integration between LOB applications and systems in an EAI scenario and trading partners in a B2B scenario. As part of this broad area of responsibility BizTalk is able to execute business processes that implement complex integration or workflow scenarios, transform data fr......

37 of 48 | BTS Guys Understand SOA and Contract First - Aaron Skonnard has put up a good post about why BTS developers understand SOA and contract first. This is a hot topic at Solidsoft Towers and James and Duncan certainly have championed this at work for some time.I was talking with James the other day about the ASHX HTTP handler that bypasses all of the unnecessary XML->Object and Object->XML deserialisation and serialisation that goes on. We agreed that as a lightweight `web service` for BTS running at the core of a SOA architecture it is essential as it reduces the evil of latency that BTS can introduce (due to its primary task of ensuring messages are durable which means trips to SQL Server that could be avoided in a request-response sy......

38 of 48 | Cool XSD Validation Function for Orchestration - As I promised in an earlier post, here`s a cool XSD validation function that can be called from within orchestration. Just add to a library - I tend to put it into a BizTalk Utilities library full of useful little functions that complement orchestration (most of which should be provided by the orchestration engine, but that`s a rant for another day!).public static void ValidateDocument( XmlDocument businessDocument, string schemaStrongName ){  // Constants  const int PARTS_IN_SCHEMA_STRONG_NAME = 2;  const int PART_CLASS_NAME = 0;  const int PART_QUALIFIED_ASSEMBLY_NAME = 1;  // Parse schema strong name  string[] assemblyNameParts ......

39 of 48 | DateTime Serialization in BizTalk - Possible Bug? - On a recent project, I came across an interesting issue with assigning the current date and time to a promoted property in a Message Assignment shape. The problem highlighted itself in our Audit database where we were auditing process state changes. The submission date of each audited record appeared to be 1 hour ahead than the current local time (based on GMT with Daylight Savings Time in effect - meaning we are currently +1 to UTC). Our scenario involves writing an audit record from the web site that is initiating the process, then each subsequent audit is performed at various steps within a BizTalk orchestration. Each audit record contains some meta data extracted from the en......

40 of 48 | BizTalk and SOA - So, it`s been a while since I`ve blogged. Life has been hectic and I`m currently spreading my time between two projects so blog time has been in short supply, even though my blog-to-do list is growing! Anyway, so what is this post all about It`s about where BizTalk fits architecturally within the new "hot" world of Service Oriented Architectures. BizTalk Server, as we know, is a middleware product that enables integration between LOB applications and systems in an EAI scenario and trading partners in a B2B scenario. As part of this broad area of responsibility BizTalk is able to execute business processes that implement complex integration or workflow scenarios, transform data from one form......

41 of 48 | BizTalk and SOA - So, it`s been a while since I`ve blogged. Life has been hectic and I`m currently spreading my time between two projects so blog time has been in short supply, even though my blog-to-do list is growing! Anyway, so what is this post all about It`s about where BizTalk fits architecturally within the new "hot" world of Service Oriented Architectures. BizTalk Server, as we know, is a middleware product that enables integration between LOB applications and systems in an EAI scenario and trading partners in a B2B scenario. As part of this broad area of responsibility BizTalk is able to execute business processes that implement complex integration or workflow scenarios, transform data from one form......

42 of 48 | BTS Guys Understand SOA and Contract First - Aaron Skonnard has put up a good post about why BTS developers understand SOA and contract first. This is a hot topic at Solidsoft Towers and James and Duncan certainly have championed this at work for some time.I was talking with James the other day about the ASHX HTTP handler that bypasses all of the unnecessary XML->Object and Object->XML deserialisation and serialisation that goes on. We agreed that as a lightweight `web service` for BTS running at the core of a SOA architecture it is essential as it reduces the evil of latency that BTS can introduce (due to its primary task of ensuring messages are durable which means trips to SQL Server that could be avoided in a request-response sy......

43 of 48 | BTS Guys Understand SOA and Contract First - Aaron Skonnard has put up a good post about why BTS developers understand SOA and contract first. This is a hot topic at Solidsoft Towers and James and Duncan certainly have championed this at work for some time.I was talking with James the other day about the ASHX HTTP handler that bypasses all of the unnecessary XML->Object and Object->XML deserialisation and serialisation that goes on. We agreed that as a lightweight `web service` for BTS running at the core of a SOA architecture it is essential as it reduces the evil of latency that BTS can introduce (due to its primary task of ensuring messages are durable which means trips to SQL Server that could be avoided in a request-response sy......

44 of 48 | DateTime Serialization in BizTalk - Possible Bug - On a recent project, I came across an interesting issue with assigning the current date and time to a promoted property in a Message Assignment shape. The problem highlighted itself in our Audit database where we were auditing process state changes. The submission date of each audited record appeared to be 1 hour ahead than the current local time (based on GMT with Daylight Savings Time in effect - meaning we are currently +1 to UTC). Our scenario involves writing an audit record from the web site that is initiating the process, then each subsequent audit is performed at various steps within a BizTalk orchestration. Each audit record contains some meta data extracted from the en......

45 of 48 | DateTime Serialization in BizTalk - Possible Bug - On a recent project, I came across an interesting issue with assigning the current date and time to a promoted property in a Message Assignment shape. The problem highlighted itself in our Audit database where we were auditing process state changes. The submission date of each audited record appeared to be 1 hour ahead than the current local time (based on GMT with Daylight Savings Time in effect - meaning we are currently +1 to UTC). Our scenario involves writing an audit record from the web site that is initiating the process, then each subsequent audit is performed at various steps within a BizTalk orchestration. Each audit record contains some meta data extracted from the en......

46 of 48 | Cool XSD Validation Function for Orchestration - As I promised in an earlier post, here`s a cool XSD validation function that can be called from within orchestration. Just add to a library - I tend to put it into a BizTalk Utilities library full of useful little functions that complement orchestration (most of which should be provided by the orchestration engine, but that`s a rant for another day!).public static void ValidateDocument( XmlDocument businessDocument, string schemaStrongName ){  // Constants  const int PARTS_IN_SCHEMA_STRONG_NAME = 2;  const int PART_CLASS_NAME = 0;  const int PART_QUALIFIED_ASSEMBLY_NAME = 1;  // Parse schema strong name  string[] assemblyNameParts = schemaStrongName.Split( new char[] { `,` }, PARTS_IN_SCHEM......

47 of 48 | Cool XSD Validation Function for Orchestration - As I promised in an earlier post, here`s a cool XSD validation function that can be called from within orchestration. Just add to a library - I tend to put it into a BizTalk Utilities library full of useful little functions that complement orchestration (most of which should be provided by the orchestration engine, but that`s a rant for another day!).public static void ValidateDocument( XmlDocument businessDocument, string schemaStrongName ){  // Constants  const int PARTS_IN_SCHEMA_STRONG_NAME = 2;  const int PART_CLASS_NAME = 0;  const int PART_QUALIFIED_ASSEMBLY_NAME = 1;  // Parse schema strong name  string[] assemblyNameParts = schemaStrongName.Split( new char[] { `,` }, PARTS_IN_SCHEM......

48 of 48 | BAM Deployment Issue - I discovered a weird problem recently when deploying a BAM definition spreadsheet using the bm.exe program.Basically, I was getting multiple message boxes containing fn_GetString in the title, plus some other blank message boxes until finally the process ended. It looked pretty terminal!The problem turned out to be that on my machine the locale was set to English (United Kingdom) and it looks like the BAM deployment process doesn`t like it. The message boxes look like they come from Excel so I guess the BAM Excel spreadsheet macro code is to blame.Changing the locale to English (United States) solved the issue and the bm.exe program was able to export the BAM definition XML successfully fro......