When opening a Visual Studio 2010 solution in Visual Studio 2012 for use in SharePoint 2013 we get this upgrade log saying we didn’t get any errors and a copy of your project was saved.

The properties.Cancel is now obsolete. Instead use properties.Status. This has several options.

When overwriting files that where already deployed in SharePoint 2010 we normally would write a lot of code to make sure the file got overwritten.

If you ever find yourself searching why on an Anonymous access page after some custom code has run you find yourself logged in then here’s why: If your using SPSecurity.

Every SharePoint developer knows where to execute stsadm. The location of the 12 hive is pounded into your brain the second that you come for the first time into contact with SharePoint.

At a customer we experienced some strange behavior of MOSS 2007.