Kong Kong de World

Upgrade is always painful. SharePoint is no exception. Microsoft has suggested two ways of upgrade: inplace and database upgrade. All articles suggest database upgrade, which is also my choice. I don't trust third party migration tools. They will mess up the whole thing as I tried the most famous one, and missed a lot of things. However I don't trust Microsoft either, maybe SharePoint itself too. Firstly I exported content database to new farm. The PowerShell window in SharePoint 2010 menu must be opened as Administrator. Run Test-SPContentDatabase in the new farm then it reported some error. Check the log it says some features are missing. Those features have already deleted but some elements still reference to them. After some search I found a tool that claims to remove even the toughest features. It's called WssRemoveFeatureFromSite written by an MS guy. Still one feature can't be deleted. My colleage suggested me to create a dummy feature using the same GUID. It...

The stsadm command was replaced by PowerShell cmdlets in 2010. To deploy on a Produciton, QA or DEV server you may probably need PowerShell scripts (with .ps1 suffix). However if you prefer GUI, you'll thank to Visual Studio 2010 as development and deployment is as simple as a few clicks.

Link to Heather Solomon's MOSS URL matrix I am a newbie in SharePoint. As what I've discovered so fat the product may be good for intranet use for medium and large organizations with out of box features, to facilitate cooperation between employees. The internet site developers, however, will immediately facing branding issue which requires master pages, page layouts, CSS, images, almost all Web Parts to be rewritten to fit "in-house" styles. C# programming is essential. Not to mention the development have to be carried on windows server family. The speed of virtual machine, compilation, deployment of features, testing loop will drive you mad. It's not impossible to re-branding, just even a medium organization won't have so much resources to feed the black hole. When I'm working on SharePoint, I couldn't stop thinking about alternative approaches... yes, Drupal, django, pure ASP.NET, even the good old LAMP. What if I could work on things like the op...

“This item cannot be deleted because it is still referenced by other pages” When you see this message when you are trying to delete MasterPage or Page Layout, use SharePoint Designer to create a new folder and move the locked item to it and then delete the folder in whole. It's the simplest work around to "unlock" the bizarre dead lock.