<?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>WF - Creating an Activity Base Class</title><link>http://blogs.msdn.com/jpricket/archive/2008/04/23/wf-creating-an-activity-base-class.aspx</link><description>(or Designing Your Workflow Activity Class Hierarchy) One of the questions that we've had to consider when designing our Workflow Activity Class Hierarchy is whether it is valuable to have our own Activity base class (derived from Activity and inherited</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Microsoft news and tips &amp;raquo; WF - Creating an Activity Base Class</title><link>http://blogs.msdn.com/jpricket/archive/2008/04/23/wf-creating-an-activity-base-class.aspx#8419660</link><pubDate>Wed, 23 Apr 2008 22:07:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8419660</guid><dc:creator>Microsoft news and tips &amp;raquo; WF - Creating an Activity Base Class</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://microsoftnews.askpcdoc.com/?p=4063"&gt;http://microsoftnews.askpcdoc.com/?p=4063&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>