Content SharePoint

Regular readers may have seen that I have been a bit quieter than usual in recent weeks - in fact I have not slacking, but working on a tool that can be useful from time to time. As I discussed in numerous posts, the deployment of SharePoint artifacts is something that is perhaps more complex than it should be, and the standard tools provided do not always simplify this picture. Personally, over my past, few projects of minimum standards, there have been several times when I thought:

• I just need to move this document library from A to B
• I just need to move these selected files (eg home page, page layouts, CSS, etc.) from A to B
• I just need to move this web from A to B
• I just need to move this site collection from A to B
• I just need to move these items 20 List from A to B

If only one easy way! CMS 2002 users can recall the SDO export mechanism that has allowed to use a TreeView to select exactly the content they want to move, but unfortunately there is a similar tool for MOSS. Of course, we have distribution of content, etc. STSADM export, but the lowest level of granularity is a network, and do not want to rewrite the whole thing can not use the option. The only other option is to write code that uses the Content Migration API. This is fine for projects that are developing the right skills and time, but otherwise things can be difficult.
Enter the Deployment Wizard for SharePoint content.
The tool provides a wizard-like approach to deploying content between SharePoint sites. The selected content is exported using the Content Migration API (PRIME), giving a. CMP (Content Migration Package) which can be copied to other servers.