First download the C+ distributable from Microsoft: Download 64
Download the CURL MSI from here:
Download CURL MSI
Install will default to this directory, and here is the curl.exe: “c:\Program Files\cURL\bin\curl.exe”.
You need to find the MSI. Many downloads of CURL will include the source code and it requires you to build it with C++ compilers and such. That’s more trouble than you usually need to go through when you just want to install and use the tool. Fortunately, the anonymous author at “ConfusedByCode.com” has been nice enough to create the MSI (Microsoft System Installer) files for CURL so that you can download it, install it, and be using it within minutes.
What is CURL?
A command line tool for getting or sending files using URL syntax.
How is CURL applicable to BizTalk or B2B Teams
B2B and BizTalk developers can use CURL to test websites, often of their trading partners. CURL can be run as part of a batch (.bat) or command (.cmd) file if you need to automate a test or schedule a download using Windows Task Scheduler.
Example Curl commands
Download the HTML of a page to your disk:
curl -o example.html www.example.com
The issue is you are testing, and it’s hard to see the exceptions you are encountering. You don’t want to go read the IIS logs, and they might not have the full .net error anyway.
1) Set customErrors mode attribute to “Off”
2) Set serviceDebug includeExceptionDetailInFaults attribute to “true”
Example of a webconfig below with these two parameters set, so you can see the context and parent nodes of where they fit in.
<compilation debug="true" targetFramework="4.0" />
<customErrors mode="Off" />
<service behaviorConfiguration="ServiceBehaviour" name="SQRT_WCF.SQRTREST">
<endpoint address="" behaviorConfiguration="web" binding="webHttpBinding"
bindingConfiguration="longTimeoutBinding" contract="SQRT_WCF.IDepot" />
<!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
<!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information -->
<serviceHostingEnvironment multipleSiteBindingsEnabled="true" />