nach oben

2013 | Buch

Pro SharePoint 2013 App Development

verfasst von: Steve Wright

Verlag: Apress

Enthalten in: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Einloggen, um Zugang zu erhalten

Über dieses Buch

Apps have taken the world by storm, and now they're taking SharePoint as well. The biggest new thing in SharePoint 2013, apps are the solution to creating custom code that runs on not just your own SharePoint deployment, but also on others' implementations as well.

Pro SharePoint 2013 App Development is your must-have guide to developing app solutions that run on the SharePoint 2013 platform. Using step-by-step tutorials, author Steve Wright creates a sample SharePoint app throughout the course of the book, and you can walk with him through the entire lifecycle of a SharePoint app.

Get expert guidance and advice on creating an app, provisioning it for use in SharePoint, securing it from unauthorized use and from other applications, integrating your app with SharePoint search and other platform features, and much more. You'll even discover how to present your app to users on mobile devices like iPads, smartphones, and Microsoft Surface tablets.

Apps in SharePoint are here to stay. Don't miss out - pick up a copy of Pro SharePoint 2013 App Development and get started on your own custom apps today.

Introduces the architecture for creating and hosting SharePoint apps. Leads the reader through the creation and deployment of a complete solution. Provides an understanding of the security features in the SharePoint app model. Helps the organization leverage internal data securely over the network. Leverages SharePoint search and other services to create rich SharePoint solutions. Introduces the techniques for delivering data on a multitude of web and mobile platforms.

Inhaltsverzeichnis

Frontmatter

Chapter 1. Introduction to SharePoint Apps

Abstract

This chapter will introduce the new SharePoint 2013 application model. We will describe why the app model exists, how it differs from the previous development models for SharePoint, and where SharePoint apps fit into the Microsoft ecosystem, including Azure, Windows 8, and Windows Phone. In this chapter, we will go over the following points:

Steve Wright

Chapter 2. Creating and Debugging Apps

Abstract

In this chapter, we will introduce the development experience for creating SharePoint apps. In traditional SharePoint development, all of the components are created in assemblies and solution packages that are deployed on the SharePoint server farm. In SharePoint apps, the components are distributed more like components in a client-server or service-oriented architecture. This makes developing and debugging these types of components significantly different from SharePoint programming in the past. In this chapter, we will go over the following points:

Steve Wright

Chapter 3. Managing the App Life Cycle

Abstract

Now that you have created the next killer app, what next? You need to distribute the app to potential users and customers. Microsoft provides a framework for deploying, updating, and removing your apps from a central App Catalog or from the SharePoint Online Store. In this chapter, we will discuss the different options you have as an app developer for managing the life cycle of your app. Our exercises will guide you through the initial deployment and an update of our Online Classroom app. In this chapter, we will go over the following points:

Steve Wright

Chapter 4. Client-Side Logic with JavaScript

Abstract

Now that we know how to create and deploy simple apps, we need to start building more sophisticated user experiences. In this chapter, we will explore the technologies that are going to help us create rich web apps that run without depending on server-side logic for routine user interface tasks. This code will run in the user's web browser and will be written in JavaScript. In this chapter, we will go over the following points:

Steve Wright

Chapter 5. Accessing the SharePoint Environment

Abstract

In the last chapter, we learned how to code application logic that runs in the user's web browser. This is important because SharePoint apps are not allowed to use server-side code running within SharePoint. Now that we have these tools, we will apply them to the core task associated with most SharePoint apps. That is interacting with objects in the SharePoint environment, including sites, lists, and documents. In this chapter, we will go over the following points:

Steve Wright

Chapter 6. SharePoint App Security

Abstract

Now we begin to put the pieces of our app together. We will begin by making sure that we cannot only present our data but protect it as well. In this chapter, we will go over the following points:

Steve Wright

Chapter 7. Web Services with REST and OData

Abstract

In Chapter 5, we learned how to use the SharePoint 2013 Client-Side Object Model (CSOM) to access SharePoint data from client applications and remote web servers. We will now use another style of interface to accomplish the same tasks using the SharePoint 2013 REST API. In this chapter, we will go over the following points:

Steve Wright

Chapter 8. Business Connectivity Services

Abstract

So far, all of the data used by our apps has resided in SharePoint. There are situations where this is not practical or desirable. For example, when our data exists in a line-of-business application such as a CRM or enterprise data warehouse, moving or replicating this data in SharePoint would be cumbersome and unreliable. Also, given the fact that our apps may be deployed in many different sites or farms, it may be difficult to access a central copy of the data in SharePoint. This situation calls for a means of accessing data stored outside of SharePoint in a way that allows our apps to provide a rich user experience while maintaining data security.

Steve Wright

Chapter 9. App Logic Components

Abstract

Now that we understand how to store, access, and manage back-end data through our SharePoint apps, let's move up a level in our solution. Let's now look at how to build the middle tier of our application. This is the level that sits between our data and the user interface and provides the business logic for our app. In this chapter, we will go over the following points:

Steve Wright

Chapter 10. Developing the User Experience

Abstract

In this chapter, we will continue moving up the levels of our architecture by looking at the user interface. We will discuss the various types of user interfaces that can be presented by apps in SharePoint and the tools that make them possible. In this chapter, we will go over the following points:

Steve Wright

Chapter 11. Accessing SharePoint Search

Abstract

In this chapter, we will begin looking at the information available from other services within SharePoint. The first of these services is SharePoint Search. We will explore the ways in which apps for SharePoint can leverage the search infrastructure in SharePoint. In this chapter, we will go over the following points:

Steve Wright

Chapter 12. Using SharePoint’s Social Features

Abstract

Social computing has become a cornerstone of modern collaboration solutions. SharePoint has always focused on collaboration using team sites. In SharePoint 2010, Microsoft introduced the ability to use social tagging with content. SharePoint 2013 adds whole new layers to the social experience. This chapter will describe the social features of the SharePoint 2013 platform and how these features can be leveraged by app developers. In this chapter, we will go over the following points:

Steve Wright

Chapter 13. Enhancing Apps with SharePoint Services

Abstract

SharePoint 2013 provides services that apps can use to better integrate with the rest of the platform. In this chapter we will explore three of these services and how we can leverage them in our apps. In this chapter, we will go over the following points:

Steve Wright

Chapter 14. Using Other App Environments

Abstract

Throughout this book, we have explored the various ways an app for SharePoint can leverage the resources of the SharePoint farm. The components that make up our apps have been hosted locally or in remote web sites outside of SharePoint to enable us to use server-side ASP.NET logic. In all cases, the custom logic for our apps has executed outside of the SharePoint server farmin a web server, a web service, or a web browser. In spite of this separation, we have always had a connection back to the SharePoint farm, in the form of context or access tokens. We have had these because our apps were always launched from inside SharePoint.

Steve Wright

Backmatter

Titel: Pro SharePoint 2013 App Development
verfasst von: Steve Wright
Verlag: Apress
Electronic ISBN: 978-1-4302-5885-8
Print ISBN: 978-1-4302-5884-1
DOI: https://doi.org/10.1007/978-1-4302-5885-8