Beginning SharePoint 2013 Development

SUMMARY

SharePoint development has fundamentally shifted its focus to provide a model that is better suited to running SharePoint in the cloud. SharePoint applications solve many of the issues of running code in the cloud by extracting the run time of that code out of the core SharePoint process and into either Windows Azure or another hosting environment of your choice.

Like many application frameworks, SharePoint provides the key mechanisms for building out your UI, event, and data layers and integrations through the use of tiles and App Parts, remote event receivers, and a comprehensive Client-Side Object Model that your application can use to call into and manipulate data in SharePoint lists and libraries, respectively.

Whether you are building a complex CRM system or a much simpler application, you should certainly consider building a SharePoint application. Your code will be transportable to SharePoint Online and available to users in that environment.

EXERCISES

You can find answers to exercises for this chapter in Appendix A.

1. What are the high-level differences of the SharePoint application model versus the older full-trust model?

2. Describe the three types of high-level integration available for SharePoint applications.

3. How does an App Part differ from a traditional Web Part?

4. How are permissions granted to an application and who can grant them?

5. How can you visually style your apps like SharePoint with little effort?

WHAT YOU LEARNED IN THIS CHAPTER ...