<?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>Partial types in Visual Basic .NET</title><link>http://blogs.msdn.com/duncanma/pages/184459.aspx</link><description>While it is good programming practice to maintain all source code for a type in a single file, sometimes a type becomes large enough that this is an impractical constraint. Furthermore, programmers often use source code generators (like the Windows Forms</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Partial types in Visual Basic .NET</title><link>http://blogs.msdn.com/duncanma/pages/184459.aspx#184507</link><pubDate>Fri, 16 Jul 2004 00:44:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:184507</guid><dc:creator>Code/Tea/Etc...</dc:creator><description /></item><item><title>A clear explanation of partial classes</title><link>http://blogs.msdn.com/duncanma/pages/184459.aspx#199056</link><pubDate>Wed, 28 Jul 2004 00:15:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:199056</guid><dc:creator>Random Thoughts of Jorriss</dc:creator><description /></item></channel></rss>