<?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>Deploying and debugging Web Parts</title><link>http://blogs.msdn.com/powlo/archive/2007/02/25/deploying-and-debugging-web-parts.aspx</link><description>When it comes to deploying and debugging your Web Part, you're spoilt for choice. My preference is to package the web part into a cab file, creating and including a manifest XML and DWP file. This should be familiar ground to seasoned web part developers,</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Displaying custom data through SharePoint lists using SPGridView and SPMenuField</title><link>http://blogs.msdn.com/powlo/archive/2007/02/25/deploying-and-debugging-web-parts.aspx#1759547</link><pubDate>Mon, 26 Feb 2007 02:49:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1759547</guid><dc:creator>Powlo's SharePoint Treats</dc:creator><description>&lt;p&gt;Step-by-step guide to using SPGridView and SPMenuField to build a Web Part which uses the standard SharePoint UI controls to render non-SharePoint data, in this case from a classic .NET DataSet.&lt;/p&gt;</description></item></channel></rss>