SharePoint 2010 ‘Page not found (404)’ page the way it should be

More and more frequently SharePoint is being used as the platform for Internet-facing websites. Not surprisingly the latest version of SharePoint is greatly improved making it event better solution for creating public websites. Although Microsoft did a great job in the Web Content Management area of SharePoint there are still a few shortcomings, one of which are custom ‘Page not found (404)’ pages. Find out how to do things right when moving your website to the SharePoint platform.

SharePoint Server MVP 2011

MVP logoI’ve just got an e-mail from Microsoft saying that I have been awarded the Microsoft Most Valuable Professional (MVP) award for another year for my contributions to the SharePoint community.

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.

Dynamically loading JavaScript from within Sandbox

SharePoint 2010 ships with the Sandbox capability that allows you to isolate custom code and run it in a safe manner. And while it offers you some great possibilities it also has some limitations as pointed recently by Wictor. One of such limitations is no access to the Page.ClientScript which is being used to register JavaScript scripts from within Web Parts. Find out how you can work around this limitation using standard capabilities of the SharePoint 2010 framework.

Productive development of SharePoint 2010 Web Content Management solutions with CKS:DEV

Developing Web Content Management (WCM) solutions on the Microsoft Office SharePoint Server (MOSS) 2007 platform was really challenging. And I’m not talking here about taking care of delivering web standards compliant XHTML, implementing accessibility or making the website lightning fast. I’m talking about the development process itself: from creating the very first custom Site Column to deploying the Solution. There were several tools, none of which fully integrated with Visual Studio or provided a consistent approach. At the end of the day we – SharePoint 2007 developers, became wizards doing the magic of manual tips & tricks and combination of various tools every day just to get the job done. Just recently, when SharePoint 2010 shipped, Microsoft provided us with the new Visual Studio 2010 SharePoint Developer Tools. And although they are called tools, they are more than that. In fact Microsoft provided us with a framework for building developer tools. A new era has come.