Question

The systems team updated a feature for me. The feature added a new favicon and a new image. The new files added in my feature where not deployed to the style library. Existing files were updated. I have opend up the wsp and the files are in there. I have opend up feature.xml and the files are mentioned there. Why could my new files not be deployed?

Était-ce utile?

La solution

From the comments in your question it seems that the system team used the Update-SpSolution PowerShell cmdlet. In that case they are performing a solution update which won't work to provision any new artifact.

As discussed in this other question SharePoint supports two main ways to upgrade a solution:

  • a retraction/readd cycle, also refered to as solution replacement
  • a solution update

To be elegible for update a solution must fall in a set of requirements, one of them is that a solution update may not add any new artifact (file, module, feature etc) or change the identity of an existing file (for example, change the id of a feature or rename a file).

Since you need to add a new file, you are bound to use the solution replacement option - remove the old solution version and add the new one. A little warning: based on your specific solution contents you may need to deactivate some feature before retraction, reactivate some of them after deploy etc or other actions required for a clean upgrade process.

Licencié sous: CC-BY-SA avec attribution
Non affilié à sharepoint.stackexchange
scroll top