Skip to content
This repository has been archived by the owner on Jan 23, 2019. It is now read-only.

Commit

Permalink
Added event receiver and infopath articles on the TOC.
Browse files Browse the repository at this point in the history
  • Loading branch information
VesaJuvonen committed Aug 12, 2016
1 parent 1265b73 commit 518a2cd
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 4 deletions.
@@ -1,8 +1,9 @@
# Sandbox solution transformation guidance - Event receivers
Transform or convert your code-based sandbox solutions to the SharePoint add-in model. Learn about the options and strategies of converting existing functionality to SharePoint add-in model or alternative solutions.
This article will help you to identify options and strategies on replacing existing event receivers from your sandbox solutions.

_**Applies to:** Add-ins for SharePoint | SharePoint 2013 | SharePoint 2016 | SharePoint Online_

Code-based sandbox solutions [were deprecated](https://blogs.msdn.microsoft.com/sharepointdev/2014/01/14/deprecation-of-custom-code-in-sandboxed-solutions/) back in 2014 and SharePoint online has started the process to completely remove this capability. Code-based sandbox solutions are also deprecated in SharePoint 2013 and in SharePoint 2016.

## Summary

Expand All @@ -15,7 +16,7 @@ The approach you take to handle events in SharePoint is slightly different in th
|**Approach**|**Additional Information**|
|:-----|:-----|
|Remote Event Receiver|</p><lu><li>[Use remote event receivers in SharePoint](https://msdn.microsoft.com/en-us/pnp_articles/use-remote-event-receivers-in-sharepoint)</li><li>[How to use remote event receivers for your SharePoint add-ins](https://channel9.msdn.com/blogs/OfficeDevPnP/How-to-use-remote-event-receivers-for-your-SharePoint-add-ins)</li><li>[Event receivers and list event receivers in the SharePoint add-in model](https://msdn.microsoft.com/en-us/pnp_articles/event-receiver-and-list-event-receiver-sharepoint-add-in)</li></lu><li>[Auto tagging sample add-in for SharePoint](https://msdn.microsoft.com/en-us/pnp_articles/autotagging-sample-app-for-sharepoint)</li><li>[Handle events in SharePoint Add-ins](https://msdn.microsoft.com/en-us/library/office/jj220048.aspx)</li></lu></p>|
|WebHooks|<p>WebHooks for SharePoint are still under development.<lu><li>[Introducing SharePoint WebHooks](http://dev.office.com/blogs/introducing-sharepoint-webhooks)</li></p>
|WebHooks|<p>WebHooks for SharePoint are still under development and will be available for preview soon.<lu><li>[Introducing SharePoint WebHooks](http://dev.office.com/blogs/introducing-sharepoint-webhooks)</li></p>
|Remote Timer Job to monitor changes|<p>Use the **ChangeQuery** object to monitor a site or list for modifications. This pattern is an alternative to Remote Event Receivers<lu><li>[SharePoint List Item Change Monitor](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.ListItemChangeMonitor)</li><li>[Remote Timer Job Pattern](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.SimpleTimerJob)</p>|

## Design Considerations
Expand All @@ -33,7 +34,7 @@ The approach you take to handle events in SharePoint is slightly different in th
- Hosting infrastructure must be highly available
- Does not support synchronous events
- Process changes after the event has occurred
- Public preview available in late 2016 for SharePoint Online
- Public preview available in summer 2016 for SharePoint Online
- Not available in SharePoint on-premises builds at this time.

### Remote Timer Job
Expand All @@ -43,7 +44,7 @@ The approach you take to handle events in SharePoint is slightly different in th

## Removing your sandbox code from your site
<a name="sectionSection3"></a>
When you deactivate your existing sandbox solution from your sites, any assets or files deployed using declarative options will not be removed however, the features in the sandbox solution will automatically be deactivated and the event receiver will be removed.
When you deactivate your existing sandbox solution from your sites, any assets or files deployed using declarative options will not be removed however, the features in the sandbox solution will automatically be deactivated and the event receiver(s) will be removed.

## Additional Resources
<a name="bk_addresources"> </a>
Expand Down
2 changes: 2 additions & 0 deletions articles/TOC.md
Expand Up @@ -80,6 +80,8 @@
### [Replace lists created from list definitions](replace-sharepoint-lists-created-from-list-definitions.md)
### [Replace Web Parts with add-in parts](replace-sharepoint-web-parts-with-add-in-parts.md)
## [Sandbox Solution Transformation Guidance](Sandbox-Solution-Transformation-Guidance.md)
### [Event receivers](Sandbox-Solution-Transformation-Guidance-Event-Receivers.md)
### [InfoPath forms with code](Sandbox-Solution-Transformation-Guidance-InfoPath.md)
## [User Profile Solutions](user-profile-solutions-for-sharepoint.md)
### [Read or update user profile properties](Read-or-update-user-profile-properties-sample-app-for-SharePoint.md)
### [Migrate user profile properties](Migrate-user-profile-properties-sample-app-for-SharePoint.md)
Expand Down

0 comments on commit 518a2cd

Please sign in to comment.