I’m a firm believer that if you build community tools which become important to folks, you’ve got to do your best to maintain them! So this is a brief post for users of my SharePoint Content Deployment Wizard and Config Store utilities. Both of these have recently been updated on Codeplex, and depending on circumstances you may want to ensure the latest versions are what you have in your toolbox. I’ll explain the changes I noted in the readme.txt of the respective updates here:
Content Deployment Wizard (2.6 beta)
This release is primarily to fix a regression bug in the 2.5 release (the first item in the list below) and provides:
- Fix to issue where lists cannot be exported with ‘All descendents’ option because menu item is missing
- Separate installers for x86 and x64 to ensure the STSADMCOMMANDS.COB.SPDEPLOYMENTWIZARD.XML file gets properly installed to 12\config directory
Also note the main new features of the 2.5 beta (included in this release):
- Support for incremental deployments, so only content which has changed since the last export gets deployed (select ‘ExportChanges’ from the dropdown to use this feature)
- Support for "no compression" deployments via the ‘Disable compression’ checkbox – this is useful for large sites where memory use is an issue during Content Deployment
- Support for allowing the root web of a site collection to be deployed on it’s own – extra options in context menus now allow selection of ‘site’ or ‘root web’. Previously it was not possible to deploy only a root web.
Should you update?
A definite yes if you downloaded the 2.5 beta release, due to the bug in that version. If you have an earlier version e.g. 1.1 or 2.0, then most likely it’s still a good idea to upgrade to the 2.6 beta as it’s fairly well tested and has some functionality you might need some day. The beta label will likely come off in a few weeks, as I know this matters to some folks.
Config Store (22.214.171.124)
Changes in this release:
- Changed internal field names back to not contain spaces – caused problem under some circumstances (an issue reported by Waldek when Config Store used with used with one of his tools)
- Changed ApplyWebConfigModifications Feature property back to True, since seems most installations use single site collection mode
- Tidied schema.xml based on recommendations made in http://mo.notono.us/2009/02/moss-dreaded-schemaxml.html
Should you update?
In this case, if you’re already using the Config Store in your site(s) it’s recommended to only consider upgrading to this version if you know you have the same problem reported by Waldek – because the field names changed, an upgrade will require some work on your part (e.g. a utility to migrate from the old schema). However, for greenfield installations, this version should definitely be used.
N.B. These Config Store changes will be ported to the Language Store framework (sister project) over the next few days.
A note on SharePoint 2010
At this stage I’m expecting my Shareutilities to continue to be useful in the 2010 world.