(If you are wondering what this blogpost is about, please read my series on Sharepoint Advanced Webparts)
Yesterday I blogged about a new series I am embarking upon. This time it will be about Sharepoint 2007 Web parts - Advanced Scenarios. I have had fantastic interaction and linkage to my DLINQ and LINQ series, so this series promises to be a lot of fun as well.
The first thing I needed to cover every damn aspect of ASP.NET 2.0 WebParts + SharePoint 2007 WebParts, and demonstrate their underworld connection with each other, was a good exemplary problem. A problem that lends me enough opportunity to demonstrate every damn aspect of this fantastic tool.
So here is the problem description -
Over the next 5-10-15 blogposts, we will be building an online RSS reader. Much like newsgator or bloglines.
There will be majorly two webparts in this operation -
a) The OPML holder
b) The RSS Rendering
I intend to first create this application inside a plain vanilla ASP.NET 2.0 Webpart framework setup. Specifically I will be using my SpareJoint framework (which I am in the final stages of clean up before turning it over as open source). We will _not_ be covering ASP.NET 2.0 Webpart framework basics. I suggest you read my article before following this series.
This example gives me sufficient flexibility to demonstrate
a) A custom editor for the OPML Holder
b) Webpart connections - ASP.NET 2.0 style.
c) And time permitting, Atlas/Ajax integration to give the user a much more seamless UI. In essence a mash up.
When we are done talking basics in ASP.NET 2.0 land, we will then take the discussion to Sharepoint. This will allow me to talk about Sharepoint specific items, and I will simply gloss over the basic webpart framework details that we have already covered.
This migration from SpareJoint to SharePoint will give me a good opportunity to talk about:
a) Security issues for the webparts in Sharepoint 2007 (hey we are doing xmldoc.load eh?)
b) Deployment tips and tricks (afterall we are moving from SpareJoint to SharePoint).
c) Page Customization - because none of the templates really have a small left column and large right column :-/.
and time permitting --
d) Demonstrate backward compatibility by leveraging the Sharepoint communication framework, by maintaining the OPML in a standard Sharepoint list rather than my custom webpart.
e) Integrate Sharepoint 2007 with Atlas and demonstrate AJAXish Mashup + ASP.NET 2.0 in a fully functional Sharepoint 2007 site.
I'm excited :).
Thou shalt -