0

I am created many Event Receivers inside SharePoint server on-premise 2013. using the following technologies:

  1. visual studio 2012.
  2. the event receivers mainly got executed when list items are updated, created on Wiki Pages and custom lists.

now my question if my current .wsp files can work as-is inside sharepoint server 2016 ? or i need to create new .wsp files using Visual studio 2015 and related tools?? Regards

2 Answers 2

1

There is no reason it should not work, unless there are problems with your code itself. Once a solution package has been deployed, your event receivers are applied to the list or library directly: there is nothing in the upgrade process that would reapply your solution package.

You can view a list of the Event Receivers currently installed using the PowerShell script below:

$url = "http://yoursiteurl" $title = "YourListTitle" $web = Get-SPWeb $url $list = $web.Lists[$title] $list.EventReceivers

4
  • i am not talking about upgrading my farm from 2013 to 2016.. i have 2 separate farms for different customers. one customer is using 2013 the other is using 2016 .. now i have an event receiver working well inside 2013, and i want to deploy the same event receiver inside 2016,, so will my wsp which i deploy inside 2013 work as-is inside 2016?? i mean will the same .wsp file work on 2013 and on 2016 ??
    – John John
    Commented Apr 6, 2017 at 23:54
  • 1
    Oh, I see. Still, the wsp architecture hadn't changed; you shouldn't have a problem there. The only potential issue would be in your code itself, and even there I can't think of any serious risks. Commented Apr 7, 2017 at 1:20
  • so the maximum risk will be that the event receiver will not work in SP 2016 is this correct ? or there could be other under the cover risks,, if i try to deploy a wsp (which i am using inside SP 2013) inside our new SP 2016 ??
    – John John
    Commented Apr 7, 2017 at 12:08
  • I cannot think of any risk to your environment at all. Commented Apr 7, 2017 at 12:10
1

We upgraded our SP2013 to SP2016. The most of our WSPs werent upgraded and all of them work as expected.

3
  • i am not talking about upgrading from 2013 to 2016 ... i have 2 separate farms for different customers. one customer is using 2013 the other is using 2016 .. now i have an event receiver working well inside 2013, and i want to deploy the same event receiver inside 2016,, so will my wsp which i deploy inside 2013 work as-is inside 2016?? i mean will the same .wsp file work on 2013 and on 2016 ??
    – John John
    Commented Apr 7, 2017 at 12:06
  • yes i think so. it is not relevant if there are two seperate farms or not. i did install my wsp seperate too. once in sharepoint 2013 server and once in 2016. it worked as expected
    – Chris K
    Commented Apr 24, 2017 at 12:17
  • If you are not sure to install the wsp at your other customer, you can simply migrate the VS Project to SP 2016. It takes about 5 minutes and we had no problems with migrating solutins yet.
    – Chris K
    Commented Apr 24, 2017 at 12:18

Your Answer

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

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