Browse by Tags

Thankfully, unlike the night of Paul Revere's fateful ride we are happy to see it coming. Side note: If you are bored go read this article talking about Israel Bissell who did the hard work. He managed to ride 345 miles to Paul's 12. Unfortunately Bissell doesn't rhyme as well as Revere. J Ok, enough history back to SharePoint. SharePoint 2013 is exciting with lots of new features. Two of the biggest will be more social capabilities and the App store. The inspiration for social feature are pretty clear, it is like a hybrid of Twitter and Facebook. That's a really good thing as we move closer to the social enterprise. The App store just makes sense. Everyone these days has more Apps than they can even imagine at their fingertips on their smart phones, it was only logical that other software would start having the same capabilities. These two features are just scratching the surface of SharePoint 2013. Fortunately, if you are interested, Microsoft has some great reading on...

This week I found a new to me issue with doing a database attach upgrade from 2007 to 2010. It seems if your 2007 content database has additional wildcard managed paths (anything other than /sites) that when you upgrade that database to SharePoint 2010 that you will end up with a bunch of explicit managed paths in SharePoint 2010. Kind of break downs like this: 2007 Wildcard managed paths: /sites /departments /projects 2007 site collections in the content database: / /sites/teamsite /departments/hr /departments/accounting /projects/CowMachine /projects/CowNinja When you create a new 2010 web application and attach the content database you will get the following managed paths: /sites - wildcard /departments/hr - explicit /departments/accounting - explicit /projects/CowMachine - explicit /projects/CowNinja - explicit And of course all of your site collections will be available. As you can quickly tell this is way less than ideal. For one when you try to create a new site collection for the...