Quickly adding assemblies references using the Object Browser

I create very often little projects to try things out: either based on the Console Application or the Class Library template. As it's SharePoint development we're speaking of the first thing you need to do is to add references to the Microsoft.SharePoint assembly. Depending on what you're doing you might need to add the references to System.Web and Microsoft.SharePoint.Publishing as well or maybe even more. You can do it just the regular way by clicking with right button on the project References and adding new reference but there is a faster way.

Slightly more accessible Web Parts

Recently, while researching the RSS Feed mechanism of the Content Query Web Part I have stumbled upon the SuppressWebPartChrome Property. As this Property sounds very promising but is not very well documented in the current WSS SDK I have decided to have a further look at it.

Inconvenient Content Editor Web Part

The Content Editor Web Part (CEWP) shipped with SharePoint 2007 is just one of these ordinary Web Parts: they don't introduce any extraordinary functionality, yet we all use them in our solutions for some reason. Because this Web Part is all about displaying the Rich Text you have entered, you might think, that it is almost impossible to mess that up. Unfortunately...

Preventing provisioning duplicate Web Parts instances on Feature reactivation

Recently I wrote about various approaches to provisioning Web Part instances in a structured and repeatable way. One of the approaches I have mentioned was using the AllUsersWebPart element within Feature manifest. While being manageable and flexible this approach has one big downside: it causes provisioning duplicate instances after the Feature has been reactivated (either by Activate-Deactivate-Activate or Activate using the -force parameter). In this article I present some possible approaches to prevent it and make your Feature provision always only one instance of each Web Part.