Introducción a las Apps para Office
Download as PPTX, PDF0 likes1,469 views
This document provides an overview of topics for developing Office 365 applications including introductory information on the Office 365 app model, deep dives into integrating Office 365 APIs into web and mobile applications, how to publish apps to the Office Store, building on the SharePoint platform, and developing on non-Microsoft stacks. It outlines core areas for Office 365 development through a series of sessions moving from introductory to more advanced deep dives.
Introducción a las Apps para Office
- 3. Intro al modelo de app Apps for Office Getting started
- 31. 2014 Introduction to Office 365 Development 2015 Deep Dive into the Office 365 App Model Deep Dive into integrating Office 365 APIs with your standalone web application development Deep Dive into integrating Office 365 APIs with your mobile device development Shipping your Office 365 App to the Office Store Deep dive into the building blocks and services of the SharePoint platform Deep Dive into Office 365 Development on non-Microsoft Stack
Editor's Notes
- #4: What new APIs are available, in preview, in the Office 365 Platform How to use these API’s in your platform of choice Some sample business scenarios for leveraging these API’s Level: Intermediate Audience: Developer Essentials
- #5: Two kinds of apps : you light up Office/Exchange/SharePoint. You consume our services in a custom (device or web) app Contextual apps Rich, powerful interactive IW experiences Do more, without leaving Excel, Outlook, PowerPoint, SharePoint Consistent Framework everywhere that Office runs. Everywhere that people do work Robust APIs Big news More for SharePoint Devs Growing up outside SharePoint Flexible Tools Open-ness and choice is a core pillar But … we just want to take away all the friction Tools targeted to specific users Platforms with best management, capability and scale What does this mean. Where is the value Breadth : more endpoints and experiences Depth: richer APIs. More capabilities Power:
- #8: To address many of the challenges developers and site owners had in previous versions of SharePoint, Microsoft has introduced a new development option for SharePoint 2013: The SharePoint App Model. In this new model apps do not necessary live within SharePoint. Instead the app’s business logic executes within the context of the client (browser) or externally from SharePoint. This external option could be another non-SharePoint Web server or a cloud server. Apps are also more secure in that when they need to access SharePoint resources such as lists and libraries they must be explicitly granted permissions to do so. This is implemented using OAuth. When an app is created, the developer specifies which permission the app needs in order to function. When the app is installed, the user installing the app is prompted to accept the permission requests the app needs (if they deny the permissions, the app is not installed). Once granted permissions, the apps can then talk to SharePoint using the Client Side Object Model (CSOM) or using some of the new OData services in SharePoint. Developers can build apps and submit them to a marketplace making it easy for customers to acquire these applications.
- #9: It’s worth spending some time taking you through how we think about modern app development at Microsoft. We have a series of products and platforms like SharePoint and Office that provide a lot of great out-of-the box functionality to help us be productive. To get even more from these products we want to be able to bring information in from other places. Services and data sources like Dynamics, Bing or something that lives out on the web or in the cloud. With the latest version of SharePoint we’re making it easier to bring together rich web services and data to create powerful new apps. Apps run outside of the SharePoint process, are hosted externally and can be exposed through REST API’s. Today there are more than 700,000 SharePoint application developers and with this release we’re providing them with a place to surface their apps through an online marketplace of rich partner solutions and applications designed to work with SharePoint and Office.
- #12: Office 2013 will continue to support the extensibility models of previous version of the Office suite. Some of these options included using things like COM Add-Ins, Macros, extensions built using Visual Studio Tools for Office (VSTO) or extending the ribbon. As with any new version, developers are strongly recommended to test these customizations in the latest version of Office 2013. The new Office 2013 extensibility model that is recommended for developers to leverage when customizing Office 2013 is to build apps. An app is founded on standard Web technologies such as HTML & JavaScript. Because they are founded on web technologies, they can generally be used in both the Office 2013 desktop and web clients. This architecture also means that they are friendly to multiple devices since they are simply executing Web technologies.
- #13: As previously covered, Office 2013 will continue to support the pre-Office 2013 extensibility models including Macros, COM Add-Ins, Ribbon customizations and those customizations built using the Visual Studio Tools for Office (VSTO). The new model in Office 2013 of building apps includes three different types of apps for Office: Task Pane: A Task Pane app, available in the Word, Excel & Project Office 2013 desktop clients and the Excel Office 2013 Web client, involves creating a task pane that runs in the left or right margin of the application. This type of extensibility option is a great solution when creating reference or lookup solutions within an application. Content: A Content app, available in the Excel Office 2013 desktop & web clients, involves adding content to a document. For instance, an Excel workbook could contain a list of stores with their addresses for a sales report. A content app within the workbook could show a map from Bing with pushpins for each of the sales locations. Mail: A Mail app, available in the Outlook Office 2013 desktop & web clients involves adding additional content based on the context of an item in Outlook. For instance an app could show a map from Bing Maps if it detects a physical address within an email.
- #14: Office 2013 introduces a new extensibility option for developers to create custom business solutions. Developers can build an app for Office, new to Office 2013, to enhance the experience when users are working within Office 2013 clients. Unlike previous extensibility models in Office, apps for Office are founded on Web technologies and therefore, depending on the type of app, can be used in both the Office 2013 desktop clients as well as the online clients. There are three different high-level scenarios that this new model supports. Each builds on the previous scenario: App for Office: This is the smallest unit of customization. Developers can build one of three types of Apps (Task Pane, Content or Contextual). These can be embedded within an Office application or within an Office document. Document Template: A document template could consist of multiple apps installed in the template document, or require an app to be installed in the hosting application. App for SharePoint: SharePoint apps can contain one or more document templates which in turn contain apps for Office. The slide contains numerous examples of each extensibility scenario.