Forum Discussion
Is GetProvisioningTemplate method able to provision assets like images, css, js?
Hi all,
I've been trying out the Pnp provisioning framework to completely replace using wsp for content database assets (such as master pages, page layouts, content types, site columns, images, css, js, etc.).
The scenario I have is a site where everything is configured (with all previously assets), and start by running the GetProvisioningTemplate on that source site. After the content is persisted to filesystem, running the ApplyProvisioningTemplate on the destination site should basically "clone" all those assets.
However, it seems the GetProvisioningTemplate is not storing artifacts such as images, css, js (although it is storing the remaining ones). Is this by design or a usage problem ?
Thanks,
Bruno
10 Replies
Hi Bruno Valente,
Are you using the Site Core or would you be happy to use the Powershell equivalent?
I'm hoping to release a set of PowerShell cripts that do exactly what you are looking for very soon. I'm going through some testing and completing the documentation.
When do you think you will be able to share those scripts ? I can assist in the testing efford (if necessary)
I was using the site.core dll framework, not the powershell. However, is it something that you have done additionally to complement the information generated by the GetProvisioningTemplate ?
Hi Bruno Valente,
I'm exporting multiple sites using the .xml file format. For each site that I want to export I'm specifying in an xml what I want to export and what I want to import. Additonally I can specify in this xml if I want to include data in lists or if I want to include content located in specified folders. This could be a document library but also easily a folder that contains display templates, images or whatever you like.
In a similar way I'm handling workarounds for known issues by updating the template.xml that is generated.
