By default SharePoint 2010 allows you to have only one version of a particular WSP deployed in the Farm. While it’s not an issue in many scenarios, as soon as you start working with multiple sites using functionality from those WSPs things will get more challenging. So how should you deal with shared components?
In my previous article I showed you how you can easily activate multiple Sandboxed Solutions at a time using Mavention Batch Sandboxed Solutions Activator. As promised, Mavention Batch Sandboxed Solutions Activator supports now Claims Based Authentication and with that SharePoint Online.
SharePoint 2010 allows you to upload multiple Sandboxed Solutions at a time. Unfortunately, unless you’re using the server object model, you will end up activating the manually one by one. Find out a more convenient way of activating multiple Sandboxed Solutions using the Mavention Batch Sandboxed Solutions Activator.
Web Templates are the new recommended approach for templating sites. Combined with Sandboxed Solutions they empower power users and offer them great flexibility and productivity. There is however one inconvenience with regard to how SharePoint Navigation Providers deal with Sandboxed Web Templates.
Using Templated Controls is a great way for separating UI from functionality. Unfortunately as soon as you customize the Master Page or Page Layouts that uses a Templated Control things are likely break. So what is exactly happening behind the scenes and, what’s more important, how should you deal with it?