none
SharePoint Designer Application Lifecycle Management RRS feed

  • Question

  • 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 type) etc. from one environment to another environment with proper release management?

    Any online resource or documentation available?

    • Edited by Nik Patel Friday, September 10, 2010 9:16 PM
    Friday, September 10, 2010 2:34 PM

All replies

  • Hi Nik, Indeed that SPD is a really great tool for no-code solutions and branding. I have not seen any guidelines or official best practice around yet like there is for VS dev. One thing I waiting for is the relase of 'Beginning SharePoint Designer 2010' in Oct, like the previous book I assume that also this will contain good recommendations about how to actually deploy and work with SPD in a real life scenarios. Btw, here comes blogposts wort to read and think about http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=204 
     http://www.sharepointhillbilly.com/archive/2009/06/12/sharepoint-solution-deployment-strategies-ndash-dare-i-say-best-practices.aspx

    / Chris


    Christian Ståhl - www.sharepointdesigners.net
    Friday, September 10, 2010 4:42 PM
  • Thanks Christian.. I will wait for more responses before marking your anwser as valid..

    I am not expecting 'Beginning SharePoint Designer 2010' book having applicable lifecycle and release management chapter.. I think its too advanced and my worst fear here is its not applicable with SPD 2010..

    What I mean by that is, if you want to use SharePoint Designer as no-code solutions then, you must develop against live site. If you planning to follow typical dev->staging->prod thenyou have to worry about many small little updates and packages in your deployment plan as shown in the link you have shared, which is totally unaccepable in real world.

    Nik

    Friday, September 10, 2010 9:09 PM
  • Hi, the previous book was worth reading in many aspects and contained a bunch of SPD best practices, but as you say there´s not so likely that the book includes a chapter like that. About your question, I think like you that this is a challenge about building complex no-code solution with SPD in the perspective to follow normal guidelines/regulations that IT-dept often has for their production environment, and regular written for code solutions (not for customizations) that can be deployed as features. Sometimes this can be doable if the SPD work is containing of just files that can just be moved from the Dev server to the Prod server, but when come to more complex scenarios we may have to do content freeze and move changes manually or as alternative switch the content databases. We look forward to see I guidelines/whitepapers about this, right!


    / Cs


    Christian Ståhl - www.sharepointdesigners.net
    Saturday, September 11, 2010 12:39 PM
  • I agree Christian.. We need proper guidelines or whitepaper on this subject especially when SPD is so powerful to build no-code solutions.. Its in high demand.. IT organizations loves these no-code solutions.. Custom code in sharepoint has become havoc and we need better guidelines for SPD solutions.. I am going to work on it and put my blog....
    Sunday, September 12, 2010 4:19 PM
  • Can anyone from Microsoft or MVP reply on this? Would love to know your thoughts. It doesn't have to be exact.. Just looking for high level authorative guidelines or best practices...
    • Marked as answer by Nik Patel Tuesday, September 21, 2010 5:03 PM
    • Unmarked as answer by Nik Patel Tuesday, September 21, 2010 5:04 PM
    Wednesday, September 15, 2010 5:02 AM
  • I know this is an old post, but for anyone else just now searching and seeing this, here are the Microsoft recommendations on SharePoint 2010 Application Lifecycle Management:

    http://msdn.microsoft.com/en-us/library/gg604045.aspx

    http://blogs.msdn.com/b/sharepointdeveloperdocs/archive/2010/11/17/application-lifecycle-management-in-microsoft-sharepoint-2010.aspx

    http://msdn.microsoft.com/en-us/sharepoint/ff420387

    Linda Chapman | SharePoint Consultant | My Blog: http://LindaChapman.BlogSpot.com | http://www.linkedin.com/in/LindaChapman

    Monday, May 14, 2012 8:28 PM