SharePoint 2010 ships with the new Ribbon framework that allows you to easily extend the Ribbon with new functionality. All Ribbon extensions consist of the UI and behavior, which in simple scenarios can be specified declaratively but in more advanced scenarios would rely on a Page Component. Most samples, that show using Page Components, suggest registering them using Delegate Controls. Unfortunately this makes it impossible to use Page Component in Sandboxed Solutions which don’t support Delegate Controls. So are we forced to use the limited declarative approach or is there a solution that would allow us to register custom Page Components within Sandboxed Solutions?
There are scenarios when you might to programmatically copy or upload a file to the Document Library in a Meeting Workspace. And while it doesn’t seem like rocket science at the first glance, there is one detail to keep in mind.
Mavention Activate Selected Features is a custom extension for the new Visual Studio 2010 SharePoint Developer Tools that allows you to select which Features should be activated when deploying the Solution in Visual Studio.
A while ago I wrote about a little tool I’ve made that help you discover the ID’s of all Site Definitions installed on the server. SharePoint requires you to provide unique ID’s for custom Site Definitions and using a tool is definitely easier than manually browsing through all the WebTemp files and noting which ID’s are already used. But who wants a tool if you can do the same with PowerShell?