Mitch Prince's Blog

Migrating Woodgrove to MOSS 2007

In the CMS migration guidance that we have delivered so far, we talk about what to look for in your existing apps, how some concepts change, and then about changes in the API.  But, we never show you actually how to migrate a site.

We are working on a whitepaper that will walk through how to migrate the Woodgrove (sample that shipped with CMS 2002) to MOSS 2007.  This is the "Hello, World" sample for CMS.  We will start off using the CMS Assessment Tool, then we will show how to use the content migration feature in MOSS, and then how to use Sharepoint Designer and VS.Net 2005 to migrate the code.  At the end of the paper will be a working example of Woodgrove on MOSS.  We will include the sample code with the paper.  From this paper you will be able to see where the different artifacts exist and some of the design decisions we made.

CMS Assessment tool Known Bugs

Since, the CMS Assessment tool was released two bugs have been reported.

The first, is a bug in the Excel spreadsheet used to display the results.  There's an error when running on non-English versions of Excel.  After hitting the “Load Analysis Results” button, you get this error.  Below is an example of what this error looks like in German:

The 2nd bug is a timeout error when running an analysis of the large CMS repositories on .Net 1.1.

We are testing fixes to both of these now and will release an update in a few weeks.

CMS Migration Materials are available and TechEd

Microsoft office Sharepoint Server 2007 (MOSS 2007) is now in Beta.  Customers of Microsoft Content Management Server 2002 (CMS 2002) maybe wondering where CMS is.  The technology in CMS has been integrated into MOSS in the Web Publishing Features.

We have written several whitepapers that discuss CMS migration to MOSS.  The start out very high level and end with an API comparision between CMS and MOSS for common tasks performed in PAPI.

In addition to these papers, we have also created a tool called the "CMS Assessment Tool".  This tool will create an inventory of every place in your application code where you are calling PAPI.  In additon to anlayzing your code, it will collect statistics from the repository, and run a pre-migration analyzer against the content to let you know of any potential content migration issues.

I placed links to all of these papers and the tool in the "CMS Migration" section on this blog.

Today, is the first keynote for TechEd.  I will be at the conference.  I will be leading a Birds of a Feather session on Thurday afternoon with Andrew Connell (MVP) on CMS Migration and you will find me at Arpan's CMS Migration talk too.