<?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>Visual Basic Issue with Types that are generated using svcutil.exe (WCF)</title><link>http://blogs.msdn.com/a_pasha/archive/2006/12/21/types-are-unitialized-if-using-visual-basic-wcf.aspx</link><description>If you generate a WCF VB proxy that contains a DataContract type using svcutil.exe , calling a method that returns the type will always incorrectly return an uninitialized type. This works correctly for C#. John Stallo, a peer of mine, spent some time</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/a_pasha/archive/2006/12/21/types-are-unitialized-if-using-visual-basic-wcf.aspx#1524988</link><pubDate>Thu, 25 Jan 2007 05:46:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1524988</guid><dc:creator>Hoop Somuah</dc:creator><description>&lt;p&gt;Ali Pasha has an interesting post about some issues you can run into when you use Visual Basic and svcutil.exe&lt;/p&gt;
</description></item><item><title>texas education agency teaching certificates</title><link>http://blogs.msdn.com/a_pasha/archive/2006/12/21/types-are-unitialized-if-using-visual-basic-wcf.aspx#4874274</link><pubDate>Wed, 12 Sep 2007 05:33:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4874274</guid><dc:creator>texas education agency teaching certificates</dc:creator><description>&lt;p&gt;texas education agency teaching certificates&lt;/p&gt;
</description></item></channel></rss>