When building extensions for Visual Studio 2010 SharePoint Developer Tools, VSIX project by default does only the packaging. Your extension’s code has to be included in a separate assembly. Did you know however that all you need is a simple trick to build your extension using a single project?
While extending SharePoint 2010 Ribbon with new functionality one of the common things you do is to check whether a command should be enabled or not. Since the checking function expects you to return a value it can get tricky if your custom checking operation is asynchronous. Find out how to asynchronously check if a Ribbon command is available.
A part of building an Internet-facing website is notifying your visitors about new content. Using RSS/Atom feeds is a common way to deliver new content to your audience. Find out how we created RSS for our brand new website without a single line of custom code!
Recently I wrote an article how you can configure the SharePoint 2010 Rich Text Editor (RTE) to better support consistent content authoring. Shortly after I published the article, I got a question how to force the RTE to allow the content editors to paste content only as plain text removing all formatting. From the consistency point of view this is a great deal especially if RTE is not your primary text editor and you’re pasting the content from another text editor. So how do you configure the SharePoint 2010 Rich Text Editor to allow pasting content only as plain text?
A while ago Microsoft provided us with Visual Studio 2010 SharePoint Power Tools – a set of productivity extensions for the Visual Studio 2010 SharePoint Developer Tools. One of the improvements shipped with the Power Tools is the Visual Web Part (Sandboxed) that – as the name says it – allows you to both benefit of the great design capabilities of Visual Web Part while still being able to deploy it to Sandbox. Unfortunately if your Sandboxed Visual Web Part will get too large things won’t be working as expected anymore.