Using Catalog Connections in SharePoint 2013 offers great flexibility with regard to content reuse within as well as across Farms. Unfortunately, as Catalog Connections are based on URLs, they break if you restore your Site Collections to different URLs. So is rebuilding Catalog Connections the only option or is there a better way to work with Catalog Connections and backup and restore of Site Collections to different URLs?
Today I got confirmed as a speaker for the upcoming SharePoint Evolutions Conference 2013 in London to present two sessions on SharePoint 2013 Web Content Management.
Visual Studio 2012 SharePoint Developer Tools have been released recently and until the new version of CKS:DEV is released you can quickly deploy your SharePoint 2013 projects using Mavention Quick Deploy.
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 the new Visual Studio 2012 RC SharePoint Developer Tools you get the ‘Cannot connect to the targeted site’ error message if you try to connect to a local site that is using a host header. Although it seems very limiting the good news is that there is a workaround.