While building BizTalk projects within Visual Studio, it is possible to receiving the following error when trying to compile a project with multiple orchestrations:
“The namespace ‘[namespace]’ already contains a definition for ‘_MODULE_PROXY_’”
While the error seems obvious, in my case, the namespaces were indeed unique, such that the above error did not make much sense. The underlying issue was in fact that the type names of two of the orchestrations within the project were identical. It turns out that an orchestration was at one point duplicated, and only the namespace was changed. After making the type names unique, the project successfully compiled and deployed.
There are a few common deployment errors in Microsoft Visual Studio when redeploying a previously deployed BizTalk project.
“Failed to add resource(s). Change requests failed for some resource. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to update binding information. Cannot update receive port “”. Transform “” not found”
Sometimes you can’t run a debugger in a local environment and you have to remotely debug your deployed code. This can be a tricky process and if there is a missed step along the way, can prove to be a pretty annoying troubleshooting process.
NOTE: In order to run a remote debugging session successfully, you’re going to need locally the exact same code base that you’re running on the server.
First you’re going to want to RDP into the machine your code is deployed on. Go to the link below, download and install the remote debugging monitor.
For our configuration we chose to not run the debugger as a service while going through the install wizard.
Here you might run into your first pitfall. While the remote debugging configuration wizard and Visual Studio are more than capable of making the correct firewall adjustments some…
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.
Azure deployments can be integrated within Visual Studio 2010, making it easy for you to package, deploy and publish your solution to an Azure cloud. This blog post will show you how to integrate your Azure deployments using Visual Studio 2010 with an easy two step process. First, you have to create a certificate within Visual Studio, and second, you have to configure your Azure environment to accept that certificate.
To create a certificate, begin by right clicking your project in the Solution Explorer pane.
Then, in the Credentials dropdown, select <Manage…>
Then, select New.
In the window that appears, 3 steps must be completed before proceeding. To complete step 1, expand the first drop down and select Create… and create a certificate. To complete step 2, click “Copy the full path”. Now, we have to digress from this dialog box and cover the…
This walkthrough will explain how to setup email alerts in TFS when there is a check-in. Using this method, you can not only select a TFS Project, but you can also select an individual folder. This is useful if you are not interested in some folders in the project, but want alerts on others.
TFS Check-In Alerts in Visual Studio 2008
First, TFS Power Tools must be installed for Visual Studio 2008 (Link), and Team Explorer (Link).
First make sure you are connected to TFS.
Tools >> Connect to Team Foundation Server…
Open Source Control Explorer.
View >> Other Windows >> Source Control Explorer.
Navigate to the folder that you want notifications on.
Right click and select “Alert on Change…”
The following popup window will display. From here you can set the alert name and the email that you want to send it to. It will try to default…
As some of you know, I presented on Entity Framework 4 and WCF Data Services 4 at Hartford Code Camp back on June 19th. I have posted the material from the code camp here.