“The name ‘InitializeControl’ does not exist in the current context” - Visual Web Part (Sandboxed) bug and how to fix it

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.

Fool-proof consistent content authoring in SharePoint 2010 Rich Text Editor

In my previous article I showed you how you can configure the SharePoint 2010 Rich Text Editor to help you do content authoring in a consistent fashion. We discussed what a Rich Text Editor should and should not allow to support consistent user experience within a website and how it can be done in SharePoint 2010. Although the configuration options of the Rich Text Editor in SharePoint 2010 allow you to achieve some neat results, it isn’t fool proof and this is exactly what we will discuss in this article: how to not only configure the RTE’s UI for consistent content authoring but also how to ensure that the authored content is consistent.

Consistent content authoring in SharePoint 2010 Rich Text Editor

Many content authors struggle with the same challenge: how to guarantee consistent content presentation across the whole website. This challenge is not SharePoint specific. No matter which Content Management System you’re using, the odds are high that sooner or later you will face it. And it’s not really surprising. Consistency is after all a trade-off: how much flexibility and functionality are you willing to give in for the control over the content presentation. Find out what you need to keep the presentation consistent across the whole site and how SharePoint 2010 can help you get this done.

SharePoint redirects revisited: using 301 instead of 302 (without code!)

Nearly a year ago I wrote an article about why you should be using permanent redirects (301) instead of temporary redirects (302) which are SharePoint defaults. Back then I presented a custom HTTP Module as a possible solution. Since then things changed a little: we have SharePoint 2010, which still has the same challenge, and we have IIS7 which allows us to get things done without a single line of code.

Automatically publishing files provisioned with Sandboxed Solutions

Sandboxed Solutions are a new capability of SharePoint 2010 that make it possible to run custom code in a safe manner. The Sandbox isolation has unfortunately some trade offs and consequences, one of which is the fact the every file you provision with a Sandboxed Solution is checked out by default. Find out how you can work around this default behavior and automatically check in all your files without too much manual effort.