Databases
StackOverflow2013
Postsdbo
POSharePoint 2007/2010 deployment methods
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSharePoint 2007/2010 deployment methods
    primarykey
    data
    text
    <p>I've been developping for SharePoint 2007/2010 for a couple years now. And I realize at this point that no company are using the same deployment method for new sites. I'm wondering what are the "Best Practices" to deploy. </p> <p>Here is the method I've used :</p> <hr> <p><strong>1 - Avoid using WSP method</strong></p> <ul> <li>Create the site in <strong>DEV</strong> using the SharePoint GUI Interface (create SubSites, Lists, Libraries, Pages, etc.). </li> <li>Customize some minor things through SharePointDesigner. </li> <li>When it's done, we package <strong>DEV</strong> using <strong>stsadm -export</strong> and then port it to <strong>QA</strong> and <strong>PROD</strong> using <strong>stsadm -import</strong>.</li> <li>When we need to make modification to an existing site, we create a Console app <strong>(.exe)</strong> that makes the necessary modifications, test it on <strong>QA</strong> then run it on <strong>PROD</strong> (and logs every operations in a separate txt file).</li> <li>We only use WSP to deploy Webparts, EventReceivers or things that would be used on different sites.</li> </ul> <hr> <p><strong>2 - Do everything in WSP method</strong></p> <ul> <li>Every time we have a new site to create, we use a provisionning WSP that creates all the content (create SubSites, Lists, Libraries, Pages, etc.) through code.</li> <li>We deploy by creating a new empty SiteCollection then install the provisionning WSP and activate it to create everything.</li> <li>When we need to make a modification to the site, we modify the WSP so it checks if things exists in code and modify what needs to change accordingly.</li> </ul> <hr> <p>I personnaly (strongly) prefer method #1 because I believe its simpler and faster. But I'd like to know some other opinions, what are the best practices in these situations? I've used method #1 for years and it worked really well actually.</p> <p>Thank you</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USdanbord
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSharePoint 2007/2010 deployment methods
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSharePoint 2007/2010 deployment methods
      1. USJosh
      1. VTFavorite
    3. VO
      singulars
      1. POSharePoint 2007/2010 deployment methods
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload