0

Suppose we have deployed a wsp (say webpart) with a feature at site collection level and it is activated.

Then, we change code of the webpart, create a new wsp.

Then, go to central admin->manage farm solutions-> retract and remove the wsp.

Then, install the new wsp using PowerShell - Add solution and PowerShell - Install solution.

Will the webpart get updated, because we had not deactivated the feature earlier, it throws error in PowerShell when we try to enable it as it is already activated at scope of sitecollection.

Improve this question
6
  • 1
    You should go with Update-SPSolution instead.
    – Christoffer
    Apr 11, 2014 at 11:22
  • So I should not retract/remove/deactivate?
    – variable
    Apr 11, 2014 at 11:22
  • If the wsp name is the same, and you've just made code changes.
    – Christoffer
    Apr 11, 2014 at 11:26
  • 1
    "To upgrade a solution, we specify which solution is to be updated and with which new solution file: Update-SPSolution –Identity MySharePointSolution.wsp –LiteralPath “D:\Deploy\MySharePointSolution.wsp” –GacDeployment"
    – Christoffer
    Apr 11, 2014 at 11:26
  • Do we have to give the scope?
    – variable
    Apr 11, 2014 at 11:29

1 Answer 1

Reset to default
1

The feature activated event will not fire again as it is already activated. However, the webpart will get updated because new dll, control templates and other components get deployed properly.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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