<p>I am now in the process of planning the deployment of a SharePoint solution into a production environment.<br>
I have read about some tools that promise an easy way to automate this process, but nothing that seems to fit my scenario.</p>

<p>In the testing phase I have used SharePoint Designer to copy site content between the different development and testing servers, but this process is manual and it seems a bit unnecessary.</p>

<p>The site is made up of SharePoint web part pages with custom web parts, and a lot of Reporting Services report definitions.</p>

<p>So, is there any good advice out there in this vast land of geeks on how to most efficiently create and deploy a SharePoint site for a multiple deployment scenario?</p>

<p><strong>Edit</strong><br>
Just to clarify. I need to deploy several "SharePoint Sites" into an existing site collection. Since SharePoint likes to have its sites in the SharePoint content database, just putting the files into IIS is not an option at this time.</p>

[{'answer_id': 9548, 'author': 'Community', 'author_id': -1, 'author_profile': 'https://Stackoverflow.com/users/-1', 'pm_score': 2, 'selected': False, 'text': '<p>We have a BizTalk 2006 with Web Application and Several WebServices that need to go from Dev to UAT to Live.</p>\n\n<p>We use MSBuild right from within VS to build, run tests, dependent on test result, complie, zip and ship to servers.</p>\n\n<p>Small MSBuild script on server to unzip, move the files, install clean web app, unlist biztalk bits, install new biztalk bits, re enlist and then start the stuff.</p>\n\n<p>MSBuild is hugh and more people need to use it as it there now right in the platform =></p>\n\n<p>Use <a href="http://msdn.microsoft.com/en-us/library/0k6kkbsd.aspx" rel="nofollow noreferrer"> MSBuild</a></p>\n'}, {'answer_id': 9643, 'author': 'Daniel McPherson', 'author_id': 897, 'author_profile': 'https://Stackoverflow.com/users/897', 'pm_score': 3, 'selected': True, 'text': '<p>I would also suggest checking out the SharePoint Content Deployment Wizard by Chris O\'Brien.\n<a href="http://www.codeplex.com/SPDeploymentWizard" rel="nofollow noreferrer">http://www.codeplex.com/SPDeploymentWizard</a> </p>\n\n<p>Should help smooth the process you describe, and it\'s a nice tool for your kitbag regardless</p>\n'}, {'answer_id': 70786, 'author': 'JacquesB', 'author_id': 7488, 'author_profile': 'https://Stackoverflow.com/users/7488', 'pm_score': 2, 'selected': False, 'text': '<p>Note that "solution" has a specific meaning in Sharepoint: a collection of features (like web parts, list definitions and so on) packaged for deployment as a .wsp file.</p>\n\n<p>You typically build sharepoint solutions in Visual Studio and package and deploy them using some tool like Sharepoint SmartTemplates <a href="http://www.codeplex.com/smarttemplates" rel="nofollow noreferrer">http://www.codeplex.com/smarttemplates</a></p>\n\n<p>However in your case you already have content in a live sharepoint site which you want to move to another site. It will probably be too cumbersome to use a solution for this, especially if you want to do it more than once (though it is possible to generate a solution from a live site using SharePoint Solution Generator). </p>\n\n<p>The easiest way to deploy all content from one live site to another is to create a backup of the site using stsadm and then restore it to the new site again using stsadm restore. This completely overwrites the new site.</p>\n\n<p>You can move select files/lists using import/export (rather than backup/restore). A tool like SharePoint Content Deployment Wizard makes it easier to select the content to move.</p>\n'}]
['https://Stackoverflow.com/questions/9543', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/960/']