How to create a package to deploy (everything)?

sharepoint.stackexchange https://sharepoint.stackexchange.com/questions/1429

Question

I've a SharePoint site which have custom Theme, Layout, WebParts (third-party - no source code), custom user controls (with source code), and the site backup (.dat) which we took from command prompt using stsadm -o backup.

Is there a way I can bundle all of them in a single package? Should I use WSPBuilder for that? If not, then please suggest.

I've experienced with SharePoint Content Deployment Manager but couldn't get any luck. It always successful while exporting a site (include all dependencies) but never succeed when you import it back gives an error: 

[2/2/2010 3:43:25 PM]: Start Time: 2/2/2010 3:43:25 PM.
[2/2/2010 3:43:25 PM]: Progress: Initializing Import.
[2/2/2010 3:43:42 PM]: FatalError: Could not find WebTemplate #75805 with LCID 1033.
   at Microsoft.SharePoint.Deployment.ImportRequirementsManager.VerifyWebTemplate(SPRequirementObject reqObj)
   at Microsoft.SharePoint.Deployment.ImportRequirementsManager.Validate(SPRequirementObject reqObj)
   at Microsoft.SharePoint.Deployment.ImportRequirementsManager.DeserializeAndValidate()
   at Microsoft.SharePoint.Deployment.SPImport.VerifyRequirements()
   at Microsoft.SharePoint.Deployment.SPImport.Run()
[2/2/2010 3:43:48 PM]: Progress: Import Completed.
[2/2/2010 3:43:48 PM]: Finish Time: 2/2/2010 3:43:48 PM.
[2/2/2010 3:43:48 PM]: Completed with 0 warnings.
[2/2/2010 3:43:48 PM]: Completed with 1 errors.
[2/2/2010 3:44:51 PM]: Start Time: 2/2/2010 3:44:51 PM.
[2/2/2010 3:44:51 PM]: Progress: Initializing Import.
[2/2/2010 3:45:08 PM]: FatalError: Could not find WebTemplate #75805 with LCID 1033.
   at Microsoft.SharePoint.Deployment.ImportRequirementsManager.VerifyWebTemplate(SPRequirementObject reqObj)
   at Microsoft.SharePoint.Deployment.ImportRequirementsManager.Validate(SPRequirementObject reqObj)
   at Microsoft.SharePoint.Deployment.ImportRequirementsManager.DeserializeAndValidate()
   at Microsoft.SharePoint.Deployment.SPImport.VerifyRequirements()
   at Microsoft.SharePoint.Deployment.SPImport.Run()
[2/2/2010 3:45:14 PM]: Progress: Import Completed.
[2/2/2010 3:45:14 PM]: Finish Time: 2/2/2010 3:45:14 PM.
[2/2/2010 3:45:14 PM]: Completed with 0 warnings.
[2/2/2010 3:45:14 PM]: Completed with 1 errors.
[2/2/2010 3:56:17 PM]: Start Time: 2/2/2010 3:56:17 PM.
[2/2/2010 3:56:17 PM]: Progress: Initializing Import.
[2/2/2010 3:56:34 PM]: FatalError: Could not find WebTemplate #75805 with LCID 1033.
   at Microsoft.SharePoint.Deployment.ImportRequirementsManager.VerifyWebTemplate(SPRequirementObject reqObj)
   at Microsoft.SharePoint.Deployment.ImportRequirementsManager.Validate(SPRequirementObject reqObj)
   at Microsoft.SharePoint.Deployment.ImportRequirementsManager.DeserializeAndValidate()
   at Microsoft.SharePoint.Deployment.SPImport.VerifyRequirements()
   at Microsoft.SharePoint.Deployment.SPImport.Run()
[2/2/2010 3:56:39 PM]: Progress: Import Completed.
[2/2/2010 3:56:39 PM]: Finish Time: 2/2/2010 3:56:39 PM.
[2/2/2010 3:56:39 PM]: Completed with 0 warnings.
[2/2/2010 3:56:39 PM]: Completed with 1 errors.

I don't know whether it has a purpose of what I am looking for. What exactly it means by above I don't have any idea.

Was it helpful?

Solution

Yes you can use WSPBuilder to package all your stuff. It's a great tool for that. You should leave the site backup out of though and restore that manually.

Regarding your error; make sure that you have installed the same features/templates on the target farm where you restore your site.

OTHER TIPS

A couple of points to consider here:

  • SharePoint isn't designed to have a single package which captures everything. Like most SharePoint 2007 developers, I'd agree with Wictor that WSPBuilder is the way to go for packaging up custom code assets such as assemblies, 12 hive files etc. - these get packaged up into Features and Solutions (.wsp). However this will not move content.
  • Backup and restore is not recommended as a way to move content between environments
  • To move content (data), the options are typically Content Deployment or STSADM export/import. When you say 'Sharepoint Content Deployment Manager', I'm guessing you mean my tool, the SharePoint Content Deployment Wizard - this uses Content Deployment to move content, and works between farms. However, as you've found in the error messages you pasted above, all the dependent files in the 12 hive (such as site definitions ['web templates' in the message]) must be present on the filesystem before the import can be successful. When you 'include dependencies' in my tool, this means dependencies between the content e.g. the master page for a given page etc., not file system dependencies as there are outside the scope of SharePoint Content Deployment.

In summary, deployment between environments in SharePoint often combines approaches e.g. WSPBuilder + Content Deployment. For further reading, check out STSADM export, Content Deployment, Content Migration API, Features/Solutions - deployment options compared.

If you have further questions, feel free to ask.

As an extension to the string above, when attempting to move a site, one may also consider 3rd party solutions such as ROSS from RepliWeb ... ROSS attempts to take into consideration the interdependencies across SharePoint assets and resolve them on target (in addition to layers of automation, etc.).

Brad (RepliWeb)

Licensed under: CC-BY-SA with attribution
Not affiliated with sharepoint.stackexchange
scroll top