SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
Did you do an upgrade solution or retract/deploy? – Wictor Wilen MCA MCM MVP Oct 28 '11 at 11:39
To be honest I don't know (it was done by the system team). I asked them to do an upgrade (that is the command I use from VS2010). – John Oct 28 '11 at 11:44
You should try and confirm if they have used the Update-SpSolution cmdlet (or any other form of solution update). If that is the case, be aware that update DOES NOT provision any new file or module - this may explain why your new file is missing and old ones get updated. – SPArchaeologist Oct 28 '11 at 12:25
Yes they used Update-SpSolution. How do i get it so new files are provisioned? – John Oct 28 '11 at 12:49
@John, please see my answer. Fell free to comment if you need further assistence. – SPArchaeologist Oct 28 '11 at 14:29
up vote 2 down vote accepted

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.

share|improve this answer
Looking more closley in VS2010 that is what it does when you do deploy. – John Oct 28 '11 at 14:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.