Waldek Mastykarz - Innovation Matters | SharePoint Server MVP | ISSN 2210-9390

A while ago I presented you the Mavention Export Page extension that allows you to export preconfigured Publishing Pages so that they can be provisioned using Features. If, however, creating Features is too much overhead to you and you are more of a PowerShell guy, you might wonder how to provision exported Publishing Pages using PowerShell. Read more »

Using structured and repeatable deployment in SharePoint 2010 solutions allows you to deliver your solution in a predictable fashion and save some time. With the SharePoint 2010 API you can script the deployment process to deliver your solution already preconfigured. Unfortunately there are some limitations in the SharePoint API that make it impossible to configure some pieces of the solution, like configuring the menu items. It turns out that it is possible after all. Find out how to programmatically configure menu items in SharePoint 2010. Read more »

Working with custom CAS policies is not trivial. Many developers find it challenging to figure out what permissions their code should have, so instead deploying safely to Web Application (BIN) they choose to deploy their assemblies to the Global Assembly Cache (GAC) granting their code full trust. There is however one trick that makes it very easy to find out what permissions you should grant to your code. Find out how to craft your custom CAS policies the easy way. Read more »

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. Read more »

Recently I’ve been working on a SharePoint solution that was persisting some state information. Originally this solution was relying on Session State but because of some extra configuration complexity that using Session State with SharePoint requires we decided to replace the Session State with cookies. Although both approaches are not exactly the same they were both sufficient in the scope of the solution. And although you might expect no rocket science when working with ASP.NET cookies there are a few things that keeping in mind might save you some painful hours. Read more »