Beginning SharePoint 2013 Development

SUMMARY

This chapter introduced you to the evolution of event receivers on the SharePoint platform: remote event receivers. Rather than relying on full-trust code deployed and running on the SharePoint server, remote event receivers are Web services where the URL is registered with SharePoint and called when an event fires on your specified SharePoint artifact. This provides the way for your app, which is executing remotely from SharePoint, to be called as events are transpiring or have transpired within your installed app on SharePoint.

Remote event receivers support both a server-to-server (behind the firewall) configuration for authentication or OAuth. In either case, appropriate authentication is required for your code to call back into SharePoint to perform a follow-on action. Both synchronous and asynchronous methods are provided for this in the web service.

Lastly, this chapter introduced you to the all-new events that fire during the app’s life cycle: when it is installed, upgraded, or uninstalling. These events round out the ability for your remote app to interact with SharePoint from its beginning install, during its execution, through its upgrade, and at the end of life.

EXERCISES

You can find answers to exercises in Appendix A.

1. What is the name of the asynchronous method in the remote event receiver?

2. If you want to cancel an event and provide an error message, what enumeration would you use on SPRemoteEventServiceStatus, and what property would you place ...