<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://markhoskins.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Mark Hoskins</title>
 <link>http://markhoskins.sys-con.com/</link>
 <description>Latest News from Mark Hoskins</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 09 Dec 2009 01:21:39 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Rapid Module Development for DotNetNuke</title>
 <link>http://markhoskins.sys-con.com/node/180968</link>
 <description>Before there were Web parts, DotNetNuke created installable private assemblies nicknamed modules to encapsulate the functionality desired within a modular environment. It doesn&#039;t take much experience developing modules for DotNetNuke before you start asking the age-old questions: I know that it&#039;s powerful, but where do I start? I know this is handled in DNN, but how? How do I structure the module and create the installable package? At this point you are most likely starting to think instinctively about how to utilize a combination of existing tools and reusable code or templates to streamline development time.&lt;p&gt;&lt;a href=&quot;http://markhoskins.sys-con.com/node/180968&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sat, 18 Feb 2006 10:45:00 EST</pubDate>
 <guid isPermaLink="true">http://markhoskins.sys-con.com/node/180968</guid>
 <comments>http://markhoskins.sys-con.com/node/180968#feedback</comments>
</item>
</channel>
</rss>
