Is there any documentation on the best practices and guidelines around the SharePoint 2010 Application Development Lifecycle Management using SharePoint Designer 2010? With all the new features in SPD 2010, it is great tool to build no-code solutions on
top of SharePoint using SPD 2010 and browser customization but it would bring new issues of application lifecycle managenet. No one wants to develop the system against production environment. How would Microsoft suggest to do no-code solutions and follow typical
application lifecycle management from dev->staging->production deployment, upgrades, release management etc.
What I am really looking for is - how would you build the sites using the SPD 2010 and package them up for the staging and production deployment including first release and subsequent releases with upgrades. I think the first time release can be easily accomplished
by packaging up the site collection developed in the development environment and restoring it in the staging and production envrionment. Things gets tricky with the subsequence releases with upgradable features without overwriting production content/data.
There are some guidelines with the Visual Studio custom development but because SPD development is tied to the sites or site collection, how would you migrate upgradable components (lists, workflows, sandbox solutions, content t
View Complete Post