A few days ago I was troubleshooting an odd error in one of our pipe delimited flat file outputs from a map. The application was just migrated from BizTalk 2004 to BizTalk 2010, and had developed a unique problem. This file was showing what seemed like random carriage returns in the output flat file.
After ruling out any errors with the generic flat file assembly pipeline or map, I pinpointed the issue being spaces contained within the input to one of the maps. The input comes from a WCF SQL request-response port, and was contained within the data itself, not artificially inserted by the adapter. Since I was using default padding (space) for the flat file, a single space in the input XML was causing the flat file send pipeline to interpret the spaces as the start of a new record entry….
Recently I came across the need to execute a command and script after a Biztalk deployment using the BizTalk Deployment Framework (BTDF). In order to accomplish this BTDF allows the use of two specific deployment ‘Targets’ in the btdfproj file. Each one will allow the execution of custom deployment or undeployment steps. The ‘CustomDeployTarget’ tag allows for execution early on in the deployment process, while the ‘CustomUndeployTarget’ allows for execution early in the undeploy process.
In order to use either, you can add the following tags to the end of the btdfproj file after the <Target Name=”CustomRedist “></Target> element:
1: <Import Project=”$(DeploymentFrameworkTargetsPath)BizTalkDeploymentFramework.targets” />
3: The Deployment Framework automatically packages most files into the server install MSI.
4: However, if there are…
Lately I have come across this annoying little bug (feature?) of Visual Studio while working with BizTalk orchestrations. If an orchestration is opened in XML view and then closed, it will forever more insist on opening up in TEXT view.
As you can see, this is not very useful. Right clicking on the orchestration in Solution Explorer, then selecting Designer, then selecting “Set as Default” does not actually set it as default either. This might be an issue with not running Visual Studio as administrator. Though in some environments, running as an administrator may not be possible. Another different solution is to open up the .btproj file containing the offending orchestration.
Recently I was tasked with migrating a Microsoft Access 2010 database to SQL Server 2008 R2 while preserving the form functionality built into Access. While the migration using Microsoft Access’ ‘Upsizing Wizard’ was easy enough for a majority of the objects, I found that a few of the more complex Access queries and tables needed manipulation or outright manual conversion to objects that both SQL Server and Access agreed with. In this two part blog series I will go through how to use the upsizing wizard to migrate an Access mdb file to an Access Project file connected to a SQL Server backend. In the second part of this series I will go over some possible roadblocks and issues that could arise, as well as their solutions.
This sample application will have a a simple form opening two parameterized queries, one…