<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.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>How to Sidestep a Visual Basic Compiler Bug in RTM </title><link>http://msmvps.com/blogs/kathleen/archive/2007/11/19/how-to-sidestep-a-visual-basic-compiler-bug-in-rtm.aspx</link><description>A couple of weeks ago I ran into a very surprising bug in the Visual Basic compiler after upgrading a project from 2005 to 2008. To make a long debugging story shorter, I realized a line of code was not included in the IL output. This particular function</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>What a nasty compiler bug !!</title><link>http://msmvps.com/blogs/kathleen/archive/2007/11/19/how-to-sidestep-a-visual-basic-compiler-bug-in-rtm.aspx#1343127</link><pubDate>Wed, 21 Nov 2007 01:15:53 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1343127</guid><dc:creator>@ Head</dc:creator><description>&lt;p&gt;Kathleen has posted about a real nasty bug in the VB 9 (VB 2008) compiler. And I mean nasty !! The compiler&lt;/p&gt;
&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1343127" width="1" height="1"&gt;</description></item></channel></rss>