<?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>Source Code Organization</title><link>http://blogs.msdn.com/b/scottdensmore/archive/2004/06/13/154715.aspx</link><description>After reading this post by Brad Abrams on source code organization, I have given this some thought. I agree with Brad and how source code is organized. Visual Studio even supports this organization in C#. In PAG we really don&amp;rsquo;t follow any sort of</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Source Code Organization</title><link>http://blogs.msdn.com/b/scottdensmore/archive/2004/06/13/154715.aspx#154762</link><pubDate>Sun, 13 Jun 2004 20:21:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:154762</guid><dc:creator>Peter Provost</dc:creator><description>Go Brad's way. I think it is more likely to be understood by developers than anything else you could come up with. It is what I recommend in my training, and what I insist my developers do.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=154762" width="1" height="1"&gt;</description></item></channel></rss>