<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Hoop Somuah : Windows Communication Foundation</title><link>http://blogs.msdn.com/hoop/archive/tags/Windows+Communication+Foundation/default.aspx</link><description>Tags: Windows Communication Foundation</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Making svcutil.exe and VisualBasic.Net play nice</title><link>http://blogs.msdn.com/hoop/archive/2007/01/24/Making-svcutil.exe-and-VisualBasic.Net-play-nice.aspx</link><pubDate>Thu, 25 Jan 2007 05:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1524974</guid><dc:creator>hoop</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/hoop/comments/1524974.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hoop/commentrss.aspx?PostID=1524974</wfw:commentRss><description>&lt;P&gt;Ali Pasha has an interesting &lt;A class="" title=post href="http://blogs.msdn.com/a_pasha/archive/2006/12/21/types-are-unitialized-if-using-visual-basic-wcf.aspx" target=_blank mce_href="http://blogs.msdn.com/a_pasha/archive/2006/12/21/types-are-unitialized-if-using-visual-basic-wcf.aspx"&gt;post&lt;/A&gt; about some issues you can run into when you use Visual Basic and svcutil.exe and I thought I'd write a post to shed some more light on the issue.&lt;/P&gt;
&lt;P&gt;DataContract types are uniquely identified using a namespace qualified name (namespace uri and a name). This namespace uri is used as the targetNamespace in XSD schemas created for that DataContract.&lt;/P&gt;
&lt;P&gt;If a namespace uri is not specified when a DataContract is created, one is automatically created based on the CLR namespace of the type and&amp;nbsp;using the prefix "&lt;EM&gt;http://schemas.datacontract.org/2004/07/"&lt;/EM&gt;. (If you do not place your types in a CLR namespace then just the prefix is used).&lt;/P&gt;
&lt;P&gt;To keep generated code as&amp;nbsp;clean as possible, the client code generator doesn't generate an explicit namespace declaration if it doesn't have to. The problem with this approach is that VB.NET projects can affect the namespace of types using a root namespace. In the abscence of an explicit namespace uri declaration, changing a types namespace will also change it's schema which will affect it's wire representation.&lt;/P&gt;
&lt;P&gt;As Ali pointed out, using the /namespace option with svcutil will fix the issue because the types namespace no longer maps directly to the auto-generated namespace and the code generator will have to explicitly define the namespace uri. Another way to make sure this doesn't happen is to define a namespace uri explicitly on the server. This should also cause the client to generate an explicit namespace uri definition.&lt;/P&gt;
&lt;P&gt;You can also work around this by not not using a root namespace in your poject.&lt;/P&gt;
&lt;P&gt;Note: This issue does not apply to service contracts because the default namespace does not affect wire communications.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1524974" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/hoop/archive/tags/Windows+Communication+Foundation/default.aspx">Windows Communication Foundation</category><category domain="http://blogs.msdn.com/hoop/archive/tags/Microsoft/default.aspx">Microsoft</category></item><item><title>.Net Framework 3.0 has Shipped!</title><link>http://blogs.msdn.com/hoop/archive/2006/11/22/net-framework-3-0-has-shipped.aspx</link><pubDate>Thu, 23 Nov 2006 04:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1125325</guid><dc:creator>hoop</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/hoop/comments/1125325.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hoop/commentrss.aspx?PostID=1125325</wfw:commentRss><description>&lt;P&gt;The first product I worked on here at Microsoft has shipped. &lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.netfx3.com/blogs/news_and_announcements/archive/2006/11/06/.NET-Framework-3.0-has-been-released_2100_.aspx" mce_href="http://www.netfx3.com/blogs/news_and_announcements/archive/2006/11/06/.NET-Framework-3.0-has-been-released_2100_.aspx"&gt;http://www.netfx3.com/blogs/news_and_announcements/archive/2006/11/06/.NET-Framework-3.0-has-been-released_2100_.aspx&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;It's a great feeling.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1125325" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/hoop/archive/tags/Windows+Communication+Foundation/default.aspx">Windows Communication Foundation</category><category domain="http://blogs.msdn.com/hoop/archive/tags/Personal/default.aspx">Personal</category><category domain="http://blogs.msdn.com/hoop/archive/tags/Microsoft/default.aspx">Microsoft</category><category domain="http://blogs.msdn.com/hoop/archive/tags/Geek/default.aspx">Geek</category></item><item><title>Back in the game</title><link>http://blogs.msdn.com/hoop/archive/2005/11/28/497685.aspx</link><pubDate>Tue, 29 Nov 2005 07:06:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:497685</guid><dc:creator>hoop</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/hoop/comments/497685.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hoop/commentrss.aspx?PostID=497685</wfw:commentRss><description>&lt;DIV&gt;After almost a year and a half of not posting to my web log, I'm going try and start up again. To start things out, I'll talk a bit about what I've been doing lately.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;For the past 2&amp;nbsp;years&amp;nbsp;or so&amp;nbsp;I've been working on the &lt;A href="http://msdn.microsoft.com/webservices/indigo/default.aspx"&gt;Windows Communication Foundation &lt;/A&gt;(formerly code-named "Indigo"). Most of the stuff I work on has something to do with implementing&amp;nbsp;Indigo's support for various metadata specifications (WSDL, WS-Metadata Exchange, WS-Policy etc.).&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Hopefully (if I do my job right), most people won't have to know or care too much what any of those specifications are. Things will just work and for the most part tools like svcutil.exe&amp;nbsp;will do the work for you.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Hopeful now that I've stuck my head out in the open again, people will let me know what kind of stuff they'd like to hear from me in this space. I'll try and make the majority of my posts here about Indigo and other closely related technologies although I may insert the occasional post or two about other technologies I'm passionate about. I don't intend to start posting on a daily basis but hopefully I'll be posting more than once every year.&lt;/DIV&gt;
&lt;DIV id=CSBloggerSig&gt;&lt;/DIV&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=497685" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/hoop/archive/tags/Windows+Communication+Foundation/default.aspx">Windows Communication Foundation</category><category domain="http://blogs.msdn.com/hoop/archive/tags/Microsoft/default.aspx">Microsoft</category></item></channel></rss>