You can reverse engineer content types using SPSource but requires Visual Studio on the dev server to run it all up properly. You can create a Solution Package using VSeWSS, WSPBuilder or STSDev and just hook SPSource into it. That way you can then simply deploy the content types using Solution Packages to each environment.
There is more information here on this (granted its light on for now...but the community would appreciate any contributions): http://www.sharepointdevwiki.com/display/public/ContentType From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Noone Sent: Wednesday, January 28, 2009 10:16 AM To: ozmoss@ozmoss.com Subject: Content Type feature Hi all, Having spent copious amounts of time developing and modifying content types in dev, I'd now like to move them to production. It seems there is no simple OOTB way to achieve this without redeploying the entire site collection. The following look very promising. Does anyone have any experience with this approach, or recommend another that doesn't involve cutting XML or CAML by hand? Content Type Viewer http://www.codeplex.com/MOSS2K7CTypesViewer An article about creating features using the Content Types Viewer http://dhunter-thinkingoutaloud.blogspot.com/2007/06/creating-content-types-with-content.html Kind regards, Paul ________________________________ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
