Visual Studio 2012 RC ships with the new SharePoint Development Tools. Unfortunately, once you pass the ‘F5’ experience and start working on some project you will notice that it’s not possible to just package your SharePoint 2013 project.
When working with external links on public-facing websites you might want the search engines not to follow them. And while you can do it without too much effort by editing the hyperlinks’ HTML, it’s just more convenient to do this via the UI. Find out how to easily prevent links from being followed using Mavention Rel Nofollow.
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.