<?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>Panel: Developers moving to VB.Net for projects using XML (Lisa Feigenbaum)</title><link>http://blogs.msdn.com/vbteam/archive/2008/11/25/c-developers-move-to-vb-for-work-with-xml-lisa-feigenbaum.aspx</link><description>Visual Basic 9.0 introduces a feature called XML Literals , which makes programming against XML a lot more natural, and dramatically decreases the number of lines of code you need to write. In fact, it makes working with XML in Visual Basic *so* much</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>VB XML Literals</title><link>http://blogs.msdn.com/vbteam/archive/2008/11/25/c-developers-move-to-vb-for-work-with-xml-lisa-feigenbaum.aspx#9143021</link><pubDate>Wed, 26 Nov 2008 03:32:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9143021</guid><dc:creator>Paul Mooney </dc:creator><description>&lt;p&gt;C# developers moving to VB.Net for projects using XMLVisual Basic 9.0 introduces a feature called XML...&lt;/p&gt;
</description></item><item><title>re: Panel: C# developers moving to VB.Net for projects using XML (Lisa Feigenbaum)</title><link>http://blogs.msdn.com/vbteam/archive/2008/11/25/c-developers-move-to-vb-for-work-with-xml-lisa-feigenbaum.aspx#9143437</link><pubDate>Wed, 26 Nov 2008 11:03:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9143437</guid><dc:creator>int19h</dc:creator><description>&lt;p&gt;While this makes sense, I still prefer C# terse syntax and extra features (such as iterators) any day. But I would really like it if I could use VB as a DSL specifically to write XML query/manipulation code. It is unfortunate that Visual Studio does not properly support the multi-language assembly scenario, even though the underlying tools are all there (compile to .netmodule &amp;amp; use al.exe, which is even supported by MSBuild via &amp;lt;AddModules&amp;gt; - but VS doesn't understand this for Intellisense and error highlighting purposes). Is there any chance that this will change in VS10?&lt;/p&gt;
</description></item><item><title>re: Panel: Developers moving to VB.Net for projects using XML (Lisa Feigenbaum)</title><link>http://blogs.msdn.com/vbteam/archive/2008/11/25/c-developers-move-to-vb-for-work-with-xml-lisa-feigenbaum.aspx#9204502</link><pubDate>Sat, 13 Dec 2008 04:22:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9204502</guid><dc:creator>mepe</dc:creator><description>&lt;p&gt;C# 4.0 will include VB language features. It is an action by Microsoft to encourage moving to C#.&lt;/p&gt;
</description></item><item><title>re: Panel: Developers moving to VB.Net for projects using XML (Lisa Feigenbaum)</title><link>http://blogs.msdn.com/vbteam/archive/2008/11/25/c-developers-move-to-vb-for-work-with-xml-lisa-feigenbaum.aspx#9204709</link><pubDate>Sat, 13 Dec 2008 04:47:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9204709</guid><dc:creator>VBTeam</dc:creator><description>&lt;p&gt;VB 10 will also include C# language features. :)&lt;/p&gt;
&lt;p&gt;We are equally pushing both VB and C#, not one over the other. The effort you are seeing is about making sure the same power is available in both.&lt;/p&gt;
</description></item></channel></rss>