<?xml version="1.0" encoding="ISO-8859-1"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exporting WSDL from WCF</title>
	<atom:link href="http://zianet.dk/blog/2007/11/26/exporting-wsdl-from-wcf/feed/" rel="self" type="application/rss+xml" />
	<link>http://zianet.dk/blog/2007/11/26/exporting-wsdl-from-wcf/</link>
	<description></description>
	<lastBuildDate>Thu, 02 Jun 2011 02:44:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: bob</title>
		<link>http://zianet.dk/blog/2007/11/26/exporting-wsdl-from-wcf/comment-page-1/#comment-151996</link>
		<dc:creator>bob</dc:creator>
		<pubDate>Thu, 06 Dec 2007 06:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://zianet.dk/blog/2007/11/26/exporting-wsdl-from-wcf/#comment-151996</guid>
		<description>get delphi update at http://cc.borland.com/Item.aspx?id=24535&amp;</description>
		<content:encoded><![CDATA[<p>get delphi update at <a href="http://cc.borland.com/Item.aspx?id=24535&#038;amp" rel="nofollow">http://cc.borland.com/Item.aspx?id=24535&#038;amp</a>;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bob</title>
		<link>http://zianet.dk/blog/2007/11/26/exporting-wsdl-from-wcf/comment-page-1/#comment-151995</link>
		<dc:creator>bob</dc:creator>
		<pubDate>Thu, 06 Dec 2007 06:13:34 +0000</pubDate>
		<guid isPermaLink="false">http://zianet.dk/blog/2007/11/26/exporting-wsdl-from-wcf/#comment-151995</guid>
		<description>just download the updated wsdl importer from http://cc.borland.com/Item.aspx?id=24535&amp;</description>
		<content:encoded><![CDATA[<p>just download the updated wsdl importer from <a href="http://cc.borland.com/Item.aspx?id=24535&#038;amp" rel="nofollow">http://cc.borland.com/Item.aspx?id=24535&#038;amp</a>;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristian Kristensen</title>
		<link>http://zianet.dk/blog/2007/11/26/exporting-wsdl-from-wcf/comment-page-1/#comment-150755</link>
		<dc:creator>Kristian Kristensen</dc:creator>
		<pubDate>Wed, 28 Nov 2007 21:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://zianet.dk/blog/2007/11/26/exporting-wsdl-from-wcf/#comment-150755</guid>
		<description>Ah I see maybe I should try that out.
I&#039;ve been having some issues in connecting a Delphi 7 client to a WCF service exposed over a basicHttpBinding. The body of the envelope from Delphi has some different namespace declarations than a std WCF client. The XML looks correct, but for some reason WCF fails to deserialize it. I haven&#039;t found a solution, but&#039;ll post it if or when I do.

Thanks for your comment and clarification!</description>
		<content:encoded><![CDATA[<p>Ah I see maybe I should try that out.<br />
I&#8217;ve been having some issues in connecting a Delphi 7 client to a WCF service exposed over a basicHttpBinding. The body of the envelope from Delphi has some different namespace declarations than a std WCF client. The XML looks correct, but for some reason WCF fails to deserialize it. I haven&#8217;t found a solution, but&#8217;ll post it if or when I do.</p>
<p>Thanks for your comment and clarification!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Restrepo</title>
		<link>http://zianet.dk/blog/2007/11/26/exporting-wsdl-from-wcf/comment-page-1/#comment-150660</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Wed, 28 Nov 2007 13:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://zianet.dk/blog/2007/11/26/exporting-wsdl-from-wcf/#comment-150660</guid>
		<description>Kristian,

The problem with your separate WSDL files is not that you have an explicit service contract (i.e. interface) defined; it&#039;s that the service contract and the service implementation have different namespaces. 

You can force them to use the same namespaces using the WCF attributes to resolve the issue without having to forgo explicit service contracts. For example, you can manipulate the XML namespace associated with a contract using the Namespace property of the [ServiceContract] attribute.</description>
		<content:encoded><![CDATA[<p>Kristian,</p>
<p>The problem with your separate WSDL files is not that you have an explicit service contract (i.e. interface) defined; it&#8217;s that the service contract and the service implementation have different namespaces. </p>
<p>You can force them to use the same namespaces using the WCF attributes to resolve the issue without having to forgo explicit service contracts. For example, you can manipulate the XML namespace associated with a contract using the Namespace property of the [ServiceContract] attribute.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

