To Web Part or not to Web Part?

Posted Monday, August 4, 2008 2:12 PM by CoreyRoth

I am putting today's post out there in a hope of getting more of a feel for what the community does in regards to web parts.  The question is when you need to write custom functionality on a SharePoint site (i.e.: a form, some fancy data binding code, whatever), do you build a web part or do you build a web user control and expose it through some sort of SmartPart.  It may be that there is a best practice here or it may just come down to personal preference.  Personally, I don't really care to do HTML markup using code.  That is not any fun at all and makes it difficult to do any kind of changes.  On the other hand if you want to make use of custom properties that the end user can customize, building a web part is the way to go.  So what do you prefer?  How do you choose what you build?  Leave a comment and let us know.

Filed under:


# re: To Web Part or not to Web Part?

Tuesday, August 5, 2008 12:53 PM by devlizard

Personally, I like SmartPart but most of the times I find myself developing web parts as custom controls.

BTW, you can always get both the easy authoring experience of ASCXs and the powerful personalization provided by wp properties by writing your own web part as your user control's wrapper (just what Smart Part does indeed).

It's an easy way to expose user controls properties to the end user.

Just my 2 cents.


Leave a Comment