<?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>Minor update to the base class guidelines</title><link>http://blogs.msdn.com/brada/archive/2003/11/21/50831.aspx</link><description>Fairly minor update -- as always, let me know if there are questions or comments. --------------------------------------------------------- Consider using abstract classes (even if there are no abstract members) if the class is designed to be a root in</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>RE: Minor update to the base class guidelines</title><link>http://blogs.msdn.com/brada/archive/2003/11/21/50831.aspx#50832</link><pubDate>Fri, 21 Nov 2003 22:35:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:50832</guid><dc:creator>Keith Patrick</dc:creator><description>Sorry for being nitpicky (hey, I *did* say I was systematic rather than pragmatic), but the return type is not part of the signature :)</description></item><item><title>RE: Minor update to the base class guidelines</title><link>http://blogs.msdn.com/brada/archive/2003/11/21/50831.aspx#50833</link><pubDate>Mon, 24 Nov 2003 05:21:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:50833</guid><dc:creator>Shane King</dc:creator><description>The ability to just throw Exception is useful. If I'm just doing something quick and dirty, I'd rather not have to make my own exception class, and just throwing an Exception is perfect. Or if I'm in the middle of building some code, I'll throw an Exception and put a TODO note against it so I can come back later and add in the proper exception without having to do it right now.

Taking away convenience for the sake of trying to force people to do the &amp;quot;right thing&amp;quot; is a bad design choice, IMO. Sometimes what you think is the right thing isn't the right thing for every situation!
</description></item><item><title>RE: Minor update to the base class guidelines</title><link>http://blogs.msdn.com/brada/archive/2003/11/21/50831.aspx#50834</link><pubDate>Mon, 24 Nov 2003 15:20:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:50834</guid><dc:creator>Ken Brubaker</dc:creator><description>Brad, thank you for these insightful updates. I am especially pleased that you explicitly reserve the Base suffix for implementation inheritance. I knew that the FCL already followed this pattern, but I had a hard time convincing my staff not to use base for public inheritance.

I have used, quite unapologetically, the Class Library Design Guidelines as my code review standard. I would LOVE to pay for an annotated reference, such as this post, in book form. Do you have any plans for publishing your Code and UI guidelines?

In response to Shane: The FCL team clearly denominates the guidelines as Class Library guidelines, not hack coding guidelines. I'm sure Brad has no problems with you using Exception in your one-off code. Just don't use it in a commercial class library. (However, you should at least use ApplicationException)
</description></item><item><title>A compilation of new .NET Design Guidelines</title><link>http://blogs.msdn.com/brada/archive/2003/11/21/50831.aspx#77091</link><pubDate>Fri, 20 Feb 2004 18:48:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:77091</guid><dc:creator>Ken Brubaker</dc:creator><description>For my own reference, I thought I'd compile a quick list of design guidelines added by Brad Abrams, et al.</description></item><item><title>re: Minor update to the base class guidelines</title><link>http://blogs.msdn.com/brada/archive/2003/11/21/50831.aspx#83093</link><pubDate>Wed, 03 Mar 2004 04:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:83093</guid><dc:creator>Kevin Dente</dc:creator><description>Brad, I was just reading through Rob Howard's discussion of the ASP.NET provider model in Whidbey. It looks like the provider classes he describes use the Base suffix, seemingly contradicting the guideline listed in this posting. Is there a particular reason for this? </description></item><item><title>Whidbey Provider Design Pattern pitfalls</title><link>http://blogs.msdn.com/brada/archive/2003/11/21/50831.aspx#93840</link><pubDate>Mon, 22 Mar 2004 15:12:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:93840</guid><dc:creator>Daniel Cazzulino .NET and XML digress</dc:creator><description /></item><item><title>Whidbey Provider Design Pattern pitfalls</title><link>http://blogs.msdn.com/brada/archive/2003/11/21/50831.aspx#93851</link><pubDate>Mon, 22 Mar 2004 15:38:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:93851</guid><dc:creator>Daniel Cazzulino .NET and XML digress</dc:creator><description /></item><item><title> Brad Abrams Minor update to the base class guidelines | patio umbrella</title><link>http://blogs.msdn.com/brada/archive/2003/11/21/50831.aspx#9772281</link><pubDate>Thu, 18 Jun 2009 06:46:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9772281</guid><dc:creator> Brad Abrams Minor update to the base class guidelines | patio umbrella</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://patioumbrellasource.info/story.php?id=257"&gt;http://patioumbrellasource.info/story.php?id=257&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>