via WCF Data Contracts and “k__BackingField” Property Naming – Nathan Bridgewater.

Related posts:

• Getting started with WCF and REST web services
• Web Services Debugging with Fiddler 2
• Referencing custom properties on a Master page from the Child page

According to Microsoft, traditional ASMX web services are now considered “Legacy technology” (!) so I thought I would buite the bullet and build the new services using WCF.

This was fairly painless until I tried to consume the web service in some old .net 1.1 web apps- when trying to add the web reference I received this error message;

Web ReferenceslocalhostReference.map(1): Custom tool warning: DiscoCodeGenerator unable to initialize code generator.  No code generated.

I found a great article over on the MSDN – and all it takes is a small change to the web.config, fiddling with, my old friend, the httpBindings.

I had to swap out the default bindings put in by .net;

        <endpoint address="" binding="wsHttpBinding" contract="HachetteErrorTracker.IErrorLog">
					<identity>
						<dns value="localhost"/>
					</identity>
				</endpoint>

For this one;

<endpoint
           address=""
           binding="basicHttpBinding" bindingNamespace="http://errortracker.localhost/"
           contract="HachetteErrorTracker.IErrorLog"
        />

How to: Configure WCF Service to Interoperate with ASP.NET Web Service Clients.

Related posts:

• Getting started with WCF and REST web services
• The provided URI scheme ‘http’ is invalid; expected ‘https
• Web Services Debugging with Fiddler 2

The provided URI scheme ‘http’ is invalid; expected ‘https

This is resolved simply by updating the web.config file and setting the security tag’s mode attribute from None to Transport;

<bindings>
<wsHttpBinding>
<binding name="WSHttpBinding_IWSHttpService" closeTimeout="00:01:00"
openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard"
maxBufferPoolSize="524288" maxReceivedMessageSize="65536"
messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true"
allowCookies="false">
<readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
maxBytesPerRead="4096" maxNameTableCharCount="16384" />
<reliableSession ordered="true" inactivityTimeout="00:10:00"
enabled="false" />
<security mode="Transport">
<transport clientCredentialType="None" proxyCredentialType="None"
realm="" />
<message clientCredentialType="None" negotiateServiceCredential="true"
algorithmSuite="Default" establishSecurityContext="true" />
</security>
</binding>
</wsHttpBinding>
</bindings>

The provided URI scheme ‘http’ is invalid; expected ‘https.

Related posts:

• Making your WCF Service compatible with legacy .net 1.1 applications
• Setting up session state database on sql server
• Running vb.net alongside c# in a web app

Related posts:

• Consuming RSS Feeds using ASP.net controls
• Web Services Debugging with Fiddler 2
• Making your WCF Service compatible with legacy .net 1.1 applications

            StringBuilder sb_xml = new StringBuilder();
            XmlSerializer s = new XmlSerializer( typeof( Hachette.Checkout.Vista.Stock.ProductStockLiteResultResponse ) );
            StringWriter w = new StringWriter(sb_xml);
            s.Serialize(w, ws_response);
            w.Close();
            Response.Write("<!-- Response = " + sb_xml + " -->");

Related posts:

• Syndicating to RSS using the built in .net SyndicationFeed classes
• A complete list of .NET Serializers in 3.5
• Web Services Debugging with Fiddler 2

Fiddler2 Web Service SOAP Debugging

The answer I’ve found is to use Fiddler2 which is a HTTP sniffer application which monitors all your HTTP traffic and allows you to inspect whats going on. So fire up fiddler2 FIRST, then fireup your test application (which generates the web service calls), place a call and watch it being logged on fiddler.

It’s imperative that you start Fiddler FIRST though or it won’t hook in and capture your SOAP calls!

You can download Fiddler 2 from here

As you can see from the screen shot on the right, the outgoing request is shown in the top right pane, and the response in the bottom right.

Related posts:

• Making your WCF Service compatible with legacy .net 1.1 applications
• How to run SQL Profiler against local SQL Express instances
• A complete list of .NET Serializers in 3.5