This is a quick and dirty solution to make sure a custom contact list can connect with Outlook and that items are actually shown.

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. One example is here.. Overwrite files in SharePoint 2010 Now with SharePoint 2013 we have an extra property to set in our elements.xml file

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.RunWithElevatedPrivileges and SPContext.Current together then the current user credentials will be elevated. Instead you should make a new reference to the Site and Web.

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. But what about us lazy developers. Those who don’t want to navigate to the bin directory and want an ease solution :-) Just copy this into your command prompt and you will be able to execute stsadm from anywhere.

At a customer we experienced some strange behavior of MOSS 2007. When a user uploaded or opened a document in a library he had no issues. But when i created a new document using the “new” button he was prompted to log in again. This behavior according to Microsoft happens in Windows 7 and Vista for the following reason.