The document provides information about an upcoming SharePoint event including logistics details like time, location, and sponsors. It also includes links to resources about Office 365 development tools and SharePoint APIs.
New holland tl80 a tractor service repair manualufjjdkksmeme
This document is a service manual for tractor models TL70A through TL100A. It contains sections on general guidelines, the engine, clutch, transmissions, and other systems. Each section provides specifications, views of components, troubleshooting information, and procedures for removal, installation, overhaul, and adjustment of parts.
Monitoring and Instrumentation Strategies: Tips and Best Practices - AppSphere16AppDynamics
This document discusses different ways to instrument software applications for monitoring purposes. It begins with definitions of instrumentation and telemetry. It then discusses the different types of data that can be collected through instrumentation like metrics and events. It describes how to instrument various parts of applications including the frontend like browsers and mobile apps as well as the backend for languages like Java, .NET, Node.js and PHP. It provides best practices for instrumentation and logging. Finally, it discusses challenges with correlating data across distributed systems and some open source options and solutions for transaction correlation.
This document discusses role mappings in Oracle Fusion, which control user access by automatically provisioning and restricting roles. It describes how to access role mappings, basic principles for auto-provisioning roles based on user attributes, making roles requestable, self-requestable, handling terminations, running auto-provisioning, and bulk loading users. Role mappings automate role assignments, restrict who can request roles, and are based on user attributes from HR records.
Este documento establece las especificaciones para redes de cableado estructurado de telecomunicaciones para edificios administrativos y áreas industriales. Incluye especificaciones para cableado horizontal y principal, distribuidores de cableado, canalizaciones, espacios para equipos y un esquema de administración para las redes de cableado. El documento contiene 11 capítulos y más de 200 páginas de detalles técnicos.
This document provides details on the design of the Fokker 100 aircraft, including:
1) Dimensions, landing distance, take-off distance, rates of climb, and cruise specifications are analyzed to determine key performance parameters.
2) The fuselage, wing, tail, and landing gear designs are outlined considering requirements and pre-dimensioning.
3) Mass and balance calculations are performed using various prediction methods to determine the maximum take-off mass and center of gravity.
4) Empennage and chassis designs are further specified, and polar determinations are made to characterize aircraft components.
5) Direct operating costs are broken down including factors like depreciation, interest, fuel
Query all roles and duties and privileges Oracle Fusion CloudFeras Ahmad
This document contains an SQL query that selects data from various tables to retrieve employee job role and privilege information. The query joins tables containing user accounts, roles, role memberships, privileges, and employee data to return fields including employee number, name, job role, duty role, assigned privileges, and navigation path for roles where the job role is either Employee or Line Manager. The results are ordered by employee number.
This document provides guidance on setting up absence management functionality in Oracle Fusion Human Capital Management for organizations in the United Arab Emirates. It outlines the order and steps for creating rate definitions, absence elements, derived factors, eligibility profiles, absence plans, and absence types to support various types of absences like annual leave, sick leave, maternity leave, and unpaid leave. It also describes how different types of absences should be recorded as transactions by users.
New holland tl80 a tractor service repair manualufjjdkksmeme
This document is a service manual for tractor models TL70A through TL100A. It contains sections on general guidelines, the engine, clutch, transmissions, and other systems. Each section provides specifications, views of components, troubleshooting information, and procedures for removal, installation, overhaul, and adjustment of parts.
Monitoring and Instrumentation Strategies: Tips and Best Practices - AppSphere16AppDynamics
This document discusses different ways to instrument software applications for monitoring purposes. It begins with definitions of instrumentation and telemetry. It then discusses the different types of data that can be collected through instrumentation like metrics and events. It describes how to instrument various parts of applications including the frontend like browsers and mobile apps as well as the backend for languages like Java, .NET, Node.js and PHP. It provides best practices for instrumentation and logging. Finally, it discusses challenges with correlating data across distributed systems and some open source options and solutions for transaction correlation.
This document discusses role mappings in Oracle Fusion, which control user access by automatically provisioning and restricting roles. It describes how to access role mappings, basic principles for auto-provisioning roles based on user attributes, making roles requestable, self-requestable, handling terminations, running auto-provisioning, and bulk loading users. Role mappings automate role assignments, restrict who can request roles, and are based on user attributes from HR records.
Este documento establece las especificaciones para redes de cableado estructurado de telecomunicaciones para edificios administrativos y áreas industriales. Incluye especificaciones para cableado horizontal y principal, distribuidores de cableado, canalizaciones, espacios para equipos y un esquema de administración para las redes de cableado. El documento contiene 11 capítulos y más de 200 páginas de detalles técnicos.
This document provides details on the design of the Fokker 100 aircraft, including:
1) Dimensions, landing distance, take-off distance, rates of climb, and cruise specifications are analyzed to determine key performance parameters.
2) The fuselage, wing, tail, and landing gear designs are outlined considering requirements and pre-dimensioning.
3) Mass and balance calculations are performed using various prediction methods to determine the maximum take-off mass and center of gravity.
4) Empennage and chassis designs are further specified, and polar determinations are made to characterize aircraft components.
5) Direct operating costs are broken down including factors like depreciation, interest, fuel
Query all roles and duties and privileges Oracle Fusion CloudFeras Ahmad
This document contains an SQL query that selects data from various tables to retrieve employee job role and privilege information. The query joins tables containing user accounts, roles, role memberships, privileges, and employee data to return fields including employee number, name, job role, duty role, assigned privileges, and navigation path for roles where the job role is either Employee or Line Manager. The results are ordered by employee number.
This document provides guidance on setting up absence management functionality in Oracle Fusion Human Capital Management for organizations in the United Arab Emirates. It outlines the order and steps for creating rate definitions, absence elements, derived factors, eligibility profiles, absence plans, and absence types to support various types of absences like annual leave, sick leave, maternity leave, and unpaid leave. It also describes how different types of absences should be recorded as transactions by users.
This document summarizes a presentation about developing provider hosted SharePoint apps. It discusses:
1) What provider hosted apps are and how they are hosted outside of SharePoint and can be developed using any language.
2) The history of customizing SharePoint and how apps differ from past methods like farm solutions.
3) The options for hosting apps, including provider hosted, autohosted, and SharePoint hosted.
4) Considerations for providers like maintaining hosting costs and updating customers.
5) The development process including using Visual Studio and the app manifest to define permissions.
6) How to authenticate with OAuth and make calls to SharePoint using the client-side object model.
Slides accompanying a presentation to SharePoint Users that also included a lot of demo not shown on slides.
The key to getting started quickly is to use a developer site on Office 365 and the Napa App. Get your free 30 day trial to Office 365 for Developers here: http://t.co/vpgmvsJHjW Also included with MSDN Subscriptions.
Provider-hosted apps are well-suited for SharePoint farms disconnected from the internet. They use digital certificates and signed access tokens to authorize access to SharePoint components like lists and libraries from remote locations. Developer tools like Visual Studio and WebMatrix can be used to create high-trust provider-hosted apps, which require deployment tasks like configuring certificates as trusted authorities in SharePoint. These apps can store and retrieve data from SharePoint and remote sources using languages like C# and APIs.
The document discusses provider-hosted apps for SharePoint that use Azure Access Control Service (ACS). ACS issues access tokens to apps using OAuth 2.0, allowing the apps to access SharePoint data and objects. Visual Studio, WebMatrix, and LightSwitch can be used to build ACS provider-hosted apps for SharePoint, which can store data in SharePoint lists, libraries, remote databases, files, and blob storage. The app provider is responsible for deploying remote components and ensuring tenant isolation.
Provider-hosted apps allow components to work across domains despite firewalls. They can access SharePoint Online and on-premises farms, and use tokens for dual authorization. A cross-domain library enables remote script to access SharePoint without tokens. Tools for building cross-domain apps include Visual Studio, LightSwitch, JavaScript, and SharePoint APIs. They can store data in SharePoint lists, libraries, remote databases, files, and blob storage.
SPCA2013 - Developing Provider-Hosted Apps for SharePoint 2013NCCOMMS
The document discusses building apps for Microsoft platforms like Office 365 and SharePoint. It provides an overview of different types of apps like immersive full-page apps, app parts, and extension apps. It also covers topics like authentication, permissions, and using APIs and services to integrate apps across platforms and devices.
Sharepoint 2013 applied architecture from the field (v2)Tihomir Ignatov
The document provides an overview of SharePoint 2013 architecture from a consultant's perspective. It discusses the role of the IT architect and considerations for SharePoint infrastructure decisions and application development. Key points covered include:
- The IT architect's responsibilities in requirements engineering, design, and solution governance.
- Factors for SharePoint infrastructure like servers, capacity planning, and skills.
- Options for developing SharePoint apps, whether cloud-hosted, on-premises, or a hybrid.
- Recommended SharePoint topologies based on availability, scalability and workload.
High-Trust Add-Ins SharePoint for On-Premises DevelopmentEdin Kapic
This document discusses high-trust app authentication for on-premises SharePoint development. It begins with an overview of the SharePoint app models and describes how high-trust apps use certificates to authenticate instead of OAuth tokens like low-trust apps. The document then covers prerequisites, the authentication mechanism, considerations, and examples of using other programming languages and extending the TokenHelper code. It concludes with information about resources for learning more about high-trust app authentication in SharePoint 2013.
Tutorial: Building Apps for SharePoint 2013 Inside and Outside of the Firewal...SPTechCon
This document provides an overview and agenda for a presentation on building apps for SharePoint 2013 both inside and outside the firewall. The presentation covers the SharePoint app model, app identity, authentication, authorization, OAuth, and client-side development. It also discusses SharePoint deployment options, the app architecture for SharePoint-hosted and cloud-hosted apps, creating app identities and permissions, and programming the client-side object model.
The document discusses SharePoint hosted add-ins. It covers topics such as setting up and deploying add-ins to both Office 365 and on-premise SharePoint, working with SharePoint lists and libraries using the JSOM and REST APIs, consuming external data sources, using the Office UI Fabric for styling, and building add-ins with TypeScript and Angular. The speaker is available to answer questions and welcomes feedback on the presentation.
This document discusses declarative deployment solutions in SharePoint and JSOM. It compares provider-hosted and SharePoint-hosted apps. Declarative solutions can deploy JavaScript, CSS, and XML files to create custom actions and site columns in a .wsp package without code. JSOM is asynchronous and slower than server-side code but can deploy to both online and on-premises environments without breaking the farm. Context is important in JSOM because objects must be explicitly requested rather than being fully available. A singleton pattern is demonstrated for organizing JSOM code to load data into global variables. Code samples are provided for live tiles and an asset gallery.
Essential Knowledge for SharePoint Add-InsInnoTech
This document discusses SharePoint add-ins, formerly known as apps. It provides an overview of add-ins, how they differ from traditional SharePoint solutions, and how to develop and install them. Add-ins allow custom code to run alongside SharePoint and can be used to integrate SharePoint with external systems, modify SharePoint sites, or add custom forms and web parts. They are developed using Visual Studio and deployed by uploading packages to the add-in catalog. Add-ins have their own identity and permission model separate from users.
Northeastern DB Class Introduction to Marklogic NoSQL april 2016Matt Turner
Here are my recommendations based on your interests:
You seem interested in SNL cast member Kristen Wiig. Based on her roles in SNL, I would recommend checking out:
- Episodes from Season 34 that featured Kristen Wiig, such as the episode from 10/4/08 where she played the character Maharelle Sister in the sketch "The Lawrence Welk Show"
- Other sketches and characters Kristen Wiig was known for on SNL like Target Lady, Dooneese, and Penelope
- Movies and TV shows Kristen Wiig has acted in since leaving SNL such as Bridesmaids, Ghostbusters, and Welcome to Me
- Learning more
The document is an XQuery tutorial by Vyacheslav Zholudev that introduces the basics of XQuery including its type system, sequences, and using XPath expressions and FLOWR expressions to query XML documents. It provides examples of getting documents with doc(), selecting nodes with XPath, using predicates, LET clauses, FOR loops, and wrapping query results.
Chris O'Brien - Comparing SharePoint add-ins (apps) with Office 365 appsChris O'Brien
A presentation I gave at SharePoint Evolutions 2015. Here, I compare SharePoint apps (now renamed "SharePoint Add-Ins" as of April 2015!) and the newer flavour of app development, Office 365 apps.
It focuses primarily on the perspective of a development team implementing the app - and factors to consider when deciding between the two approaches. However, to do this we must consider end-user and administration aspects, as well as code/development.
Key agenda points:
- Changes in SharePoint development
- Apps, 2 years on..
- SharePoint Add-Ins – a recap
- Office 365 apps - Why did Microsoft introduce these? What do they promise?
- Comparing SharePoint Add-Ins with Office 365 apps - For the end-user, administrator and developer
- Summary
Rev Your Engines - SharePoint Performance Best PracticesEric Shupps
This document discusses techniques for enhancing SharePoint performance, including:
- Optimizing the database through techniques like content archiving, cleanup, and index maintenance.
- Distributing the database and cache across multiple servers to improve scalability and availability.
- Implementing request management to route requests based on rules to balance load and isolate traffic.
- Improving the user interface through techniques like client-side rendering, optimized markup, and image renditions to reduce page weight.
SharePoint 2013 introduces a new way to extend sites using apps that can be self-contained, cloud-hosted, or provider-hosted. There are three types of apps: full page apps that fill the entire page, app parts that surface in an iframe, and extension apps that extend the ribbon or menus. Apps can be SharePoint-hosted using only HTML/JavaScript, auto-hosted on Azure, or provider-hosted using custom infrastructure. Apps provide benefits like increased stability, easier maintenance, and quicker delivery, but have limitations around server-side code and customizing SharePoint features.
Build Secure Cloud-Hosted Apps for SharePoint 2013Danny Jessee
Apps for SharePoint were introduced in SharePoint 2013 to maximize the level of capability and flexibility that developers can deliver without risking compromise to the farm. In this session, we will delve into apps that leverage resources running outside the SharePoint farm—whether in another on-premises web server or in the cloud. We will use server-side and client-side code to demonstrate how cloud-hosted apps can securely access data stored in SharePoint using the client object model (CSOM/JSOM) and REST APIs, along with the pros and cons associated with each approach. We will discuss the various permissions models associated with apps for SharePoint including types of app permissions, permission request scopes, and how app developers can manage permissions. We will conclude by building and provisioning a provider-hosted app for SharePoint to Office 365.
This document discusses how to automate tasks in SharePoint Online (Office 365) using PowerShell and the Client-Side Object Model (CSOM). It provides an overview of the history and challenges of using CSOM for provisioning in O365. It also demonstrates how to connect to O365 using PowerShell and CSOM, and highlights resources for learning and developing with this approach. The session aims to help developers and IT professionals automate SharePoint Online administration.
This document summarizes a presentation about developing provider hosted SharePoint apps. It discusses:
1) What provider hosted apps are and how they are hosted outside of SharePoint and can be developed using any language.
2) The history of customizing SharePoint and how apps differ from past methods like farm solutions.
3) The options for hosting apps, including provider hosted, autohosted, and SharePoint hosted.
4) Considerations for providers like maintaining hosting costs and updating customers.
5) The development process including using Visual Studio and the app manifest to define permissions.
6) How to authenticate with OAuth and make calls to SharePoint using the client-side object model.
Slides accompanying a presentation to SharePoint Users that also included a lot of demo not shown on slides.
The key to getting started quickly is to use a developer site on Office 365 and the Napa App. Get your free 30 day trial to Office 365 for Developers here: http://t.co/vpgmvsJHjW Also included with MSDN Subscriptions.
Provider-hosted apps are well-suited for SharePoint farms disconnected from the internet. They use digital certificates and signed access tokens to authorize access to SharePoint components like lists and libraries from remote locations. Developer tools like Visual Studio and WebMatrix can be used to create high-trust provider-hosted apps, which require deployment tasks like configuring certificates as trusted authorities in SharePoint. These apps can store and retrieve data from SharePoint and remote sources using languages like C# and APIs.
The document discusses provider-hosted apps for SharePoint that use Azure Access Control Service (ACS). ACS issues access tokens to apps using OAuth 2.0, allowing the apps to access SharePoint data and objects. Visual Studio, WebMatrix, and LightSwitch can be used to build ACS provider-hosted apps for SharePoint, which can store data in SharePoint lists, libraries, remote databases, files, and blob storage. The app provider is responsible for deploying remote components and ensuring tenant isolation.
Provider-hosted apps allow components to work across domains despite firewalls. They can access SharePoint Online and on-premises farms, and use tokens for dual authorization. A cross-domain library enables remote script to access SharePoint without tokens. Tools for building cross-domain apps include Visual Studio, LightSwitch, JavaScript, and SharePoint APIs. They can store data in SharePoint lists, libraries, remote databases, files, and blob storage.
SPCA2013 - Developing Provider-Hosted Apps for SharePoint 2013NCCOMMS
The document discusses building apps for Microsoft platforms like Office 365 and SharePoint. It provides an overview of different types of apps like immersive full-page apps, app parts, and extension apps. It also covers topics like authentication, permissions, and using APIs and services to integrate apps across platforms and devices.
Sharepoint 2013 applied architecture from the field (v2)Tihomir Ignatov
The document provides an overview of SharePoint 2013 architecture from a consultant's perspective. It discusses the role of the IT architect and considerations for SharePoint infrastructure decisions and application development. Key points covered include:
- The IT architect's responsibilities in requirements engineering, design, and solution governance.
- Factors for SharePoint infrastructure like servers, capacity planning, and skills.
- Options for developing SharePoint apps, whether cloud-hosted, on-premises, or a hybrid.
- Recommended SharePoint topologies based on availability, scalability and workload.
High-Trust Add-Ins SharePoint for On-Premises DevelopmentEdin Kapic
This document discusses high-trust app authentication for on-premises SharePoint development. It begins with an overview of the SharePoint app models and describes how high-trust apps use certificates to authenticate instead of OAuth tokens like low-trust apps. The document then covers prerequisites, the authentication mechanism, considerations, and examples of using other programming languages and extending the TokenHelper code. It concludes with information about resources for learning more about high-trust app authentication in SharePoint 2013.
Tutorial: Building Apps for SharePoint 2013 Inside and Outside of the Firewal...SPTechCon
This document provides an overview and agenda for a presentation on building apps for SharePoint 2013 both inside and outside the firewall. The presentation covers the SharePoint app model, app identity, authentication, authorization, OAuth, and client-side development. It also discusses SharePoint deployment options, the app architecture for SharePoint-hosted and cloud-hosted apps, creating app identities and permissions, and programming the client-side object model.
The document discusses SharePoint hosted add-ins. It covers topics such as setting up and deploying add-ins to both Office 365 and on-premise SharePoint, working with SharePoint lists and libraries using the JSOM and REST APIs, consuming external data sources, using the Office UI Fabric for styling, and building add-ins with TypeScript and Angular. The speaker is available to answer questions and welcomes feedback on the presentation.
This document discusses declarative deployment solutions in SharePoint and JSOM. It compares provider-hosted and SharePoint-hosted apps. Declarative solutions can deploy JavaScript, CSS, and XML files to create custom actions and site columns in a .wsp package without code. JSOM is asynchronous and slower than server-side code but can deploy to both online and on-premises environments without breaking the farm. Context is important in JSOM because objects must be explicitly requested rather than being fully available. A singleton pattern is demonstrated for organizing JSOM code to load data into global variables. Code samples are provided for live tiles and an asset gallery.
Essential Knowledge for SharePoint Add-InsInnoTech
This document discusses SharePoint add-ins, formerly known as apps. It provides an overview of add-ins, how they differ from traditional SharePoint solutions, and how to develop and install them. Add-ins allow custom code to run alongside SharePoint and can be used to integrate SharePoint with external systems, modify SharePoint sites, or add custom forms and web parts. They are developed using Visual Studio and deployed by uploading packages to the add-in catalog. Add-ins have their own identity and permission model separate from users.
Northeastern DB Class Introduction to Marklogic NoSQL april 2016Matt Turner
Here are my recommendations based on your interests:
You seem interested in SNL cast member Kristen Wiig. Based on her roles in SNL, I would recommend checking out:
- Episodes from Season 34 that featured Kristen Wiig, such as the episode from 10/4/08 where she played the character Maharelle Sister in the sketch "The Lawrence Welk Show"
- Other sketches and characters Kristen Wiig was known for on SNL like Target Lady, Dooneese, and Penelope
- Movies and TV shows Kristen Wiig has acted in since leaving SNL such as Bridesmaids, Ghostbusters, and Welcome to Me
- Learning more
The document is an XQuery tutorial by Vyacheslav Zholudev that introduces the basics of XQuery including its type system, sequences, and using XPath expressions and FLOWR expressions to query XML documents. It provides examples of getting documents with doc(), selecting nodes with XPath, using predicates, LET clauses, FOR loops, and wrapping query results.
Chris O'Brien - Comparing SharePoint add-ins (apps) with Office 365 appsChris O'Brien
A presentation I gave at SharePoint Evolutions 2015. Here, I compare SharePoint apps (now renamed "SharePoint Add-Ins" as of April 2015!) and the newer flavour of app development, Office 365 apps.
It focuses primarily on the perspective of a development team implementing the app - and factors to consider when deciding between the two approaches. However, to do this we must consider end-user and administration aspects, as well as code/development.
Key agenda points:
- Changes in SharePoint development
- Apps, 2 years on..
- SharePoint Add-Ins – a recap
- Office 365 apps - Why did Microsoft introduce these? What do they promise?
- Comparing SharePoint Add-Ins with Office 365 apps - For the end-user, administrator and developer
- Summary
Rev Your Engines - SharePoint Performance Best PracticesEric Shupps
This document discusses techniques for enhancing SharePoint performance, including:
- Optimizing the database through techniques like content archiving, cleanup, and index maintenance.
- Distributing the database and cache across multiple servers to improve scalability and availability.
- Implementing request management to route requests based on rules to balance load and isolate traffic.
- Improving the user interface through techniques like client-side rendering, optimized markup, and image renditions to reduce page weight.
SharePoint 2013 introduces a new way to extend sites using apps that can be self-contained, cloud-hosted, or provider-hosted. There are three types of apps: full page apps that fill the entire page, app parts that surface in an iframe, and extension apps that extend the ribbon or menus. Apps can be SharePoint-hosted using only HTML/JavaScript, auto-hosted on Azure, or provider-hosted using custom infrastructure. Apps provide benefits like increased stability, easier maintenance, and quicker delivery, but have limitations around server-side code and customizing SharePoint features.
Build Secure Cloud-Hosted Apps for SharePoint 2013Danny Jessee
Apps for SharePoint were introduced in SharePoint 2013 to maximize the level of capability and flexibility that developers can deliver without risking compromise to the farm. In this session, we will delve into apps that leverage resources running outside the SharePoint farm—whether in another on-premises web server or in the cloud. We will use server-side and client-side code to demonstrate how cloud-hosted apps can securely access data stored in SharePoint using the client object model (CSOM/JSOM) and REST APIs, along with the pros and cons associated with each approach. We will discuss the various permissions models associated with apps for SharePoint including types of app permissions, permission request scopes, and how app developers can manage permissions. We will conclude by building and provisioning a provider-hosted app for SharePoint to Office 365.
This document discusses how to automate tasks in SharePoint Online (Office 365) using PowerShell and the Client-Side Object Model (CSOM). It provides an overview of the history and challenges of using CSOM for provisioning in O365. It also demonstrates how to connect to O365 using PowerShell and CSOM, and highlights resources for learning and developing with this approach. The session aims to help developers and IT professionals automate SharePoint Online administration.
Come riprogettare le attuali farm solution di share point con il nuovo modell...Fabio Franzini
This document discusses redesigning existing SharePoint Farm Solutions using the new SharePoint app model. It covers the evolution of SharePoint development, the new app model, types of apps, the SharePoint 2013 remote API including CSOM and REST, and how to convert existing WSP solutions to the new app framework. Examples of converting common farm solution artifacts like web parts, event receivers, and workflows are also provided.
Metalogix roadshow 2016 Paris - Keynote SharePoint et Office 365Patrick Guimonet
The document discusses new features in SharePoint 2016 including enhanced controls for document libraries, increased list and file size thresholds, MinRole for defining server roles, hybrid scenarios for connecting on-premises and Office 365 environments, and new capabilities like Flow for automating business processes across apps and services. It also demonstrates Office 365 Groups, the Office Graph, and hybrid search functionality.
- SharePoint can be used for web content management and public websites (DotCom sites), but they require a different approach than internal intranet sites.
- When developing DotCom sites, special considerations are needed around the business needs, end user experience, performance, hardware requirements, authentication, branding, and authoring experience to ensure success.
- Thorough testing is critical to address performance, cross-browser compatibility, and user experience on both desktop and mobile.
Real World SharePoint Framework and Azure ServicesBrian Culver
Building Solution in Office 365 requires leveraging other cloud services, such as Azure Services. For those new to SharePoint and all SharePoint veterans, building cloud ready “Full Trust” solutions for Office 365 introduces a huge paradigm shift over the traditional on-premise full-trust development model.
In this session, we will look at a couple common full trust solutions and move them to Office365 and Azure. We will leverage various Azure services such as Azure Functions, Event Grids and WebJobs. See demonstrations on how event receivers become Azure Function and Event Grids, and timer jobs become Azure WebJobs. Learn about other useful Azure services for replacing full trust functionality. Don’t pass up this opportunity to learn skills and knowledge you need to build Office 365 Solutions leveraging Cloud Services
Attendee Takeaways:
1. Understand how to take Full Trust solutions from On-premise to the Office365.
2. Learn how to use Azure Functions, Event Grids, WebJobs and several other Azure Services.
3. See demonstrations of a couple common Full Trust Solutions converted to cloud solutions on Office365 and Azure.
This document provides an overview of SharePoint and guidance for working with the platform. It begins with an introduction to SharePoint that outlines its popularity and capabilities. It then covers logical architecture, governance, the paths for different user roles, development tools, debugging techniques, deployment strategies, and the importance of the community for support. Helpful tips are provided throughout for avoiding common pitfalls when working with SharePoint.
Real World SharePoint Framework and Azure ServicesBrian Culver
Building Solution in Office 365 requires leveraging other cloud services, such as Azure Services. For those new to SharePoint and all SharePoint veterans, building cloud ready “Full Trust” solutions for Office 365 introduces a huge paradigm shift over the traditional on-premise full-trust development model.
In this session, we will look at a couple common full trust solutions and move them to Office365 and Azure. We will leverage various Azure services such as Azure Functions, Event Grids and WebJobs. See demonstrations on how event receivers become Azure Function and Event Grids, and timer jobs become Azure WebJobs. Learn about other useful Azure services for replacing full trust functionality. Don’t pass up this opportunity to learn skills and knowledge you need to build Office 365 Solutions leveraging Cloud Services
Attendee Takeaways:
1. Understand how to take Full Trust solutions from On-premise to the Office365.
2. Learn how to use Azure Functions, Event Grids, WebJobs and several other Azure Services.
3. See demonstrations of a couple common Full Trust Solutions converted to cloud solutions on Office365 and Azure.
Recorded for SharePoint Saturday VA Beach 2019
If you are like me, you love InfoPath. Even if you don't love it, you probably have respect for it (even if grudgingly). It had been around for a long time and we have done some amazing things with it but it could be a bit decrepit at times. Along comes PowerApps and it is awesome and continually getting better but it's no InfoPath... Yet. In this session, we will look at the differences between the two and when to use each.
It is well known that with the release of SharePoint 2013, Microsoft is shifting its recommended method for customizing and building applications to a client side “App Model” development paradigm.
This has caused many organizations to invest large amounts of time and energy in rewriting solutions or to stop customizing SharePoint and building solutions altogether.
In this session we will cover:
- The current limitations with developing enterprise solutions using the App Model and only client side technologies
- The key decision points when architecting your solutions
- How to determine when the App Model approach is the right solution for your project, when it may NOT be the right solution.
- How to architect and deliver full trust solutions in a way that will allow you to convert your solution and move to the cloud in a seamless and low impact way.
Building SharePoint 2013 Apps - Architecture, Authentication & Connectivity APISharePointRadi
This document provides an overview of building SharePoint 2013 apps, including their architecture, authentication, and connectivity APIs. It discusses the app infrastructure and how apps work, authentication models for apps, and the Connectivity API for accessing SharePoint data from apps. The presentation also covers server-side and client-side app hosting models, app shapes including full pages and parts, and the app manifest and package.
Share point 2013: introduction, features, and rolesVinh Nguyen
SharePoint is a browser-based collaboration and content management platform from Microsoft. This article provides an introduction to SharePoint 2013, including its features, roles, and how to install it. It describes SharePoint's main features such as document management and collaboration. It also outlines the typical roles involved like architect, developer, administrator, and user. Finally, it provides guidance on hardware and software requirements for installing SharePoint 2013.
- Paramdeep Singh Saini is a SharePoint professional with almost 5 years of experience who holds a Bachelor's degree in Electronics and Communications.
- He has extensive experience designing and developing custom SharePoint solutions using tools like Visual Studio, SharePoint Designer, and InfoPath.
- Currently he works as a Senior SharePoint Developer at Vodafone Shared Services India where he designs and develops solutions using the SharePoint client object model and leads a team of SharePoint developers.
SPSToronto 2015 - Managing Office365 with PowerShell and CSOMamitvasu
This document discusses how to automate tasks in SharePoint Online (Office 365) using PowerShell and the Client-Side Object Model (CSOM). It provides an overview of managing content types and site columns in O365 without using declarative code. It then demonstrates how to use CSOM and PowerShell to provision and manage content types and site columns remotely. The document includes a history of the presenter's experience with PowerShell and CSOM, an example of CSOM code, and resources for learning more.
This document provides an introduction to SharePoint development for .NET developers. It discusses the SharePoint platform editions, when to develop on the SharePoint platform, development tools and approaches such as the client object model, and resources for learning more about SharePoint development.
Business Intelligence session on the SharePoint and Office set of BI features to build and integrate data-driven spreadsheets and applications with SharePoint 2010. This session will cover topics such as PowerPivot, PerformancePoint Services, Reporting Services, Excel Services, KPIs, and much more
The document discusses using SharePoint Portal Server to integrate various enterprise applications. It outlines customer scenarios for application integration and self-service portals. It then describes SharePoint's strategy and tools for building composite applications that connect to backends like SAP and Siebel using web services, web parts, and BizTalk integration. Examples are provided for connecting to SAP and Siebel systems and developing single sign-on portals.
Creating Business Intelligence with SharePoint 2010Ivan Sanders
This document discusses creating business intelligence with SharePoint 2010. It outlines dashboards, scorecards, Excel Services, and PowerPivot technology. It describes slicing and dicing data in Excel 2010 and SharePoint. Visio Services and its key features of sharing diagrams and connecting them to data sources to build dashboards are also covered. The document discusses authoring and publishing reports and providing rich visualizations of geospatial data. Codeplex sites with source code and SharePoint 2010 guidance resources are listed.
SharePoint Intersections - SP09 - Introduction to SharePoint 2013 for IT ProsDan Usher
The document provides an introduction to new features in SharePoint 2013 for IT professionals, covering improvements to infrastructure, services, user interface and developer story. It highlights key changes such as distributed database and cache services, shredded storage, workflow and social collaboration updates, and the new apps model. Hardware and software requirements are also outlined.
Semelhante a Build and Deploy Provider-hosted SharePoint Add-ins (20)
Updating Legacy SharePoint Customizations to the Add-in ModelDanny Jessee
This document discusses migrating legacy SharePoint customizations to the add-in model. It covers categorizing different types of customizations, such as UI, declarative, and timer job customizations. It then provides techniques for updating each category, such as using the SharePoint PnP provisioning engine to remotely provision assets and running timer jobs from external applications. The overall approach is to apply customizations with a "lighter touch" and leverage the SharePoint add-in model.
Build Secure Cloud-Hosted Apps for SharePoint 2013Danny Jessee
Apps for SharePoint were introduced in SharePoint 2013 to maximize the level of capability and flexibility that developers can deliver without risking compromise to the farm. In this session, we will delve into apps that leverage resources running outside the SharePoint farm—whether in another on-premises web server or in the cloud. We will use server-side and client-side code to demonstrate how cloud-hosted apps can securely access data stored in SharePoint using the client object model (CSOM/JSOM) and REST APIs, along with the pros and cons associated with each approach. We will discuss the various permissions models associated with apps for SharePoint including types of app permissions, permission request scopes, and how app developers can manage permissions. We will conclude by building and provisioning a provider-hosted app for SharePoint to Office 365.
Build Secure Cloud-Hosted Apps for SharePoint 2013Danny Jessee
Apps for SharePoint were introduced in SharePoint 2013 to maximize the level of capability and flexibility that developers can deliver without risking compromise to the farm. In this demo-intensive session, we will delve into apps that leverage resources running outside the SharePoint farm—whether in another on-premises web server or in the cloud. We will use server-side and client-side code to demonstrate how cloud-hosted apps can securely access data stored in SharePoint using the client object model (CSOM/JSOM) and REST APIs, along with the pros and cons associated with each approach. We will discuss the various permissions models associated with apps for SharePoint including types of app permissions, permission request scopes, and how app developers can manage permissions.
Put it on a Map! Using the new Location and Map Features in SharePoint 2013Danny Jessee
SharePoint 2013 introduces a new “Geolocation” field type that makes it easy to store location-based information in lists. SharePoint can then be configured to display this data automatically on a Bing map. In this session, we will demonstrate how to configure the SharePoint environment to support geolocation data and how developers can leverage these new features to incorporate location, mapping, and proximity features into their applications.
Get Started with Apps for SharePoint 2013!Danny Jessee
This document is a collection of hyperlinks to Microsoft web pages and online resources that provide documentation and guidance for developing apps and solutions for Microsoft SharePoint and Office 365. The links cover topics like setting up app domains, consuming and connecting to SharePoint and Office 365 APIs, authentication, authorization, and various development frameworks and tools.
Get Started with Apps for SharePoint 2013!Danny Jessee
This document provides a list of over 40 URLs and web links related to developing apps and services for Microsoft SharePoint and Office. The links reference resources on the SharePoint and Office developer portals on MSDN, tutorials for building SharePoint apps, setting up development environments, using the SharePoint and Office REST APIs, and blogs with guidance from Microsoft experts.
Get Started with Apps for SharePoint 2013Danny Jessee
This document contains a list of over 50 URLs linking to Microsoft developer documentation and other resources for creating apps for the SharePoint 2013 platform. The URLs provide information on setting up app domains, making SharePoint REST calls, using the SharePoint client object model, and other topics relevant to SharePoint app development.
SharePoint 2010, Claims-Based Identity, Facebook, and the CloudDanny Jessee
The document discusses integrating Facebook authentication with SharePoint 2010. It covers authentication vs authorization, configuring an Azure Access Control Service as an identity provider, and adding claims mappings in SharePoint. Code examples are provided for retrieving a user's Facebook access token, making calls to the Facebook Graph API to get profile data, and storing that data in SharePoint lists and user profiles. The document recommends requesting minimum permissions from Facebook and using a full read permission policy for Facebook users in SharePoint.
SharePoint 2010, Claims-Based Identity, Facebook, and the CloudDanny Jessee
The document provides information about integrating Facebook authentication with SharePoint 2010. It discusses using Azure Access Control Service (ACS) to configure Facebook as an identity provider and map claims from Facebook to SharePoint. It also describes how to retrieve user data from Facebook using the access token and Graph API after authentication. The document includes code snippets and step-by-step instructions for setting up Facebook authentication with SharePoint.
Claims-Based Identity, Facebook, and the CloudDanny Jessee
This document provides information about integrating Facebook authentication with SharePoint 2010. It discusses using Azure AppFabric Access Control Service (ACS) to configure Facebook as an identity provider for SharePoint. The steps include creating a Facebook application, configuring ACS for Facebook support, and configuring ACS as a trusted identity provider in SharePoint. Code examples show how to retrieve user information from Facebook and make calls to the Facebook Graph API once a user is authenticated. The document emphasizes that claims-based authentication allows decoupling authentication from authorization and personalization.
SharePoint 2010,Claims-Based Identity, Facebook, and the CloudDanny Jessee
The document discusses integrating Facebook authentication with SharePoint 2010. It covers:
1. Configuring an app in Facebook and Azure ACS to enable Facebook login and pass claims to SharePoint.
2. Configuring SharePoint to trust tokens from ACS and map claims to SharePoint properties.
3. Using the Facebook access token to call the Facebook API and retrieve user data to display in SharePoint.
SharePoint 2010, Claims-Based Identity, Facebook, and the CloudDanny Jessee
This document provides information about Danny Jessee, a senior software engineer with 8 years of SharePoint development experience. It includes his credentials, contact information, and topics he can present on, such as features of secure applications, SharePoint 2010 authentication options, claims terminology and technology overview. It also lists some demos he can provide, including setting up a new SharePoint 2010 web application, integrating Facebook authentication using Azure AppFabric ACS, and further integrating Facebook data into SharePoint using the Facebook C# SDK.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Choosing The Best AWS Service For Your Website + API.pptx
Build and Deploy Provider-hosted SharePoint Add-ins
1.
2. Housekeeping…
• Download EventBoard Mobile and remember to fill out session
evaluations…
• http://app.spsdc.org
• Phasers set to stun, mobile devices set to silent…
• You must be present to win at the wrap-up…
4. Join us at #SharePint sponsored by Kemp Technologies at
World of Beer of Reston in the Towncenter just across
the bridge
Why? To network with fellow SharePoint professionals
What? SharePint!!!
When? 6:15 PM
Where?
World of Beer Reston
1888 Explorer Street
Reston, VA 20190
Thanks to
Kemp Technologies
14. $(document).ready(function () {
hostweburl = decodeURIComponent(getQueryStringParameter("SPHostUrl"));
$.getScript(hostweburl + "/_layouts/15/SP.UI.Controls.js", renderChrome);
});
function renderChrome() {
var options = {
"appIconUrl": decodeURIComponent(getQueryStringParameter("SPHostLogoUrl")),
"appTitle": "CSOM/JSOM/REST demos",
"onCssLoaded": "chromeLoaded()"
};
// Place the chrome control in the <div> with ID="chrome_ctrl_placeholder"
var nav = new SP.UI.Controls.Navigation("chrome_ctrl_placeholder", options);
nav.setVisible(true);
}
34. URL Returns
_api/web/title The title of the current site
_api/web/lists/getByTitle('Announcements') The Announcements list
_api/web/lists/getByTitle('Announcements')/fields The columns in the Announcements list
_api/web/lists/getByTitle('Tasks')/items The items in the Tasks list
_api/web/siteusers The users in the site
_api/web/sitegroups The user groups in the site
_api/web/GetFolderByServerRelativeUrl('/Shared
Documents')
The root folder of the Shared Documents
library
_api/web/GetFolderByServerRelativeUrl('/Plans')
/Files('a.txt')/$value
The file a.txt from the Plans library
Table adapted from http://msdn.microsoft.com/en-us/magazine/dn198245.aspx
36. CSOM REST
Less “chatty” (requests can be batched) More “chatty” (request batching can only be
done in Office 365, not on-premises)
Handles the “plumbing” of calls to SharePoint Requires you to construct and manage your
own HTTPRequest/Response objects
Requires CAML for queries Uses standard OData vocabularies
Can interact with managed metadata
taxonomies and workflows
No support for interacting with managed
metadata taxonomies and workflows
Easy to leverage third-party libraries (jQuery)
Can be debugged using Fiddler
No external assembly references required
Table adapted from http://www.andrewconnell.com/blog/sharepoint-2013-csom-vs.-rest-...-my-preference-and-why
46. Requirement/Scenario OAuth Cross-domain
I use client-side technologies (HTML + JavaScript).
I want to use REST interfaces.
There is a firewall between SharePoint and my remote Add-
in, and I need to issue the calls through the browser.
My Add-in needs to access resources as the logged-on user.
My Add-in needs to elevate privileges to other than those of
the current logged-on user.
My Add-in needs to act on behalf of a user other than the
one who is logged on.
My Add-in needs to perform operations only while the user
is logged on.
My Add-in needs to perform operations even when the user
is not logged on.
Table from http://msdn.microsoft.com/en-us/library/fp179897.aspx
47.
48.
49. key ClientId value xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
key ClientSecret value xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
An app package is a ZIP file with a .app extension. If you create a new SharePoint app project named MyFirstApp, the project will generate a app package named MyFirstApp.app as its output. Note that the file format for creating an app package is based on the Open Package Convention (OPC) format. This is the same file format that Microsoft Office begin to use with the release of Office 2007 for creating Word documents (docx) and Excel workbooks (xlsx).
So now you understand one of the key points of the SharePoint app model. Custom code never runs inside SharePoint. It runs somewhere else. You have the option of writing both client-side code and server-side code. A SharePoint-hosted app is easier to create, implement and deploy. However, it does not provide the opportunity to add server-side code. A cloud-hosted app will yield more power because you can write as much server-side code as you would like using a managed language such as C# and your code is not limited by all those frustrating limitations and issues created by running code inside the SharePoint environment.
You can do a lot more with the app manifest, such as use different authentication schemes (also known as app principals, declare what permissions the app needs to run, and other tasks. Also, do you notice strings like “{StandardTokens}” in the app manifest shown above? These are tokens that are replaced at build/run time. These tokens allow you to reference your app and also pass context (for example, the SharePoint language, where the app is installed, and so on). To learn more about what you can do with the app manifest and tokens, see App for SharePoint manifest file.
Within apps, SharePoint 2013 decouples server-side code from the server, enabling you to run server-side code from outside SharePoint, in the cloud. You can host server-side code in autohosted and provider-hosted apps.
It is the presence of an inner solution package inside the app package file that tells the SharePoint host whether it needs to create an app web during installation. If the app package does not contains an inner solution package, the SharePoint host installs the app without creating an app web. The inner solution package for a SharePoint app should contain a single Web-scoped feature. The SharePoint host activates this feature automatically on the app web immediately after the app web is created. This features is what makes it possible to add declarative elements such as pages and lists as the app is installed. However, the inner solution package for a SharePoint app cannot contain any type of DLL or any .NET code whatsoever.
You are responsible for creating the installation, upgrade, and uninstallation logic of the remote components.
If you look back at the AppManifest.xml file shown earlier, you notice that it did not include a hard-coded path to the app’s start page. Instead, the URL to the start page contains a dynamic token named ~appWebUrl. This dynamic token is replaced by the SharePoint host when the app is installed. This makes sense because the URL that will be used to access the app web is not even known until the SharePoint host creates a new domain for the app during installation. After creating the app web, the SharePoint host can then use it to create the URL to the start page.
So why doesn’t the SharePoint host serve up pages from the app web using the same domain as the host site? At first, the reasons why the SharePoint host serves up the pages from an app web in their own isolated domain might not be obvious. There are two primary reasons why the SharePoint app model does this. Both of these reasons are related to security and the management and enforcement of permissions granted to an app.
The first reason for isolating an app web in its own private domain has to do with preventing direct JavaScript calls from pages in the app web back to the host site. This security protection of the SharePoint app model builds on the browser’s built-in support for prohibiting cross-site scripting (XSS). Since JavaScript code running on pages from an app web pages originates from a different domain, this code cannot directly call back to the host site. More specifically, calls from JavaScript running on app web pages do not run with the same identity nor the same permissions as JavaScript code behind pages in the host site.
Can have multiple user experiences within an app
Can have multiple user experiences within an app
Can have multiple user experiences within an app
<F5> deploy/debugging experience (JavaScript and .NET code)
When SharePoint “starts” an app i.e. when a user launches an app, SharePoint packs up some information about that user and passes it along to the app as a POST parameter. This is called the ContextToken and it contains OAuth tokens/information that you need in order to make calls back to SharePoint. Now the trick is that SharePoint passes it to your app when it launches and then it is up to you to do something like cache it so that in subsequent page requests your app has that context and can reuse it. The basic auth token in it is good for 12 hours & it also contains a refresh token that can be used to get new auth tokens for up to 6 months.
When you make the GetSharePointContext(HttpContext) call the class checks the ASP.Net Session state for an existing context. If it doesn’t find one then it creates a new one based on the information passed and then stashes it in Session state for subsequent requests.
Then on subsequent requests, when SP hasn’t passed any new tokens, the GetSharePointContext(HttpContext) will return you back the context from Session state. It will also deal with when and if tokens expire.
We will discuss authN/authZ in greater detail later
Keep your Office dev tools up to date…there were lots of issues with these in early releases!
Classes are the same in provider-hosted or autohosted app projects (same in Web Forms or MVC web application projects)
The way I look at it is that I can do just about everything I need to do using the CSOM within a specific site collection.
The REST interface on the other hand is mostly brand new in the SharePoint 2013 release. There was a single service in SharePoint 2010 that we could use that enabled read/write to data within a list. The current REST implementation covers a huge area of SharePoint 2013.
Rob Windsor Pluralsight course
Need to get a SharePoint context because we are outside the SharePoint server
With a SharePointContext, we can get the necessary ClientContext
Same basic steps as CSOM:
Create a ClientContext object, passing in the URL of a SharePoint site
Call the Load() function to build the request query for any value properties your application needs to access
Execute the query by calling the ExecuteQuery() function
Not a complete code sample
Not a complete code sample
HTTP verbs match to CRUD operations
HTTP verbs match to CRUD operations
Pros and cons on both sides, matter of personal preference
Azure ACS is used as an authorization server (Automatically set up with O365)
User-only – if no permissions are requested by the app (Created by user)
User+app – default if permissions are requested by the app (Created by SharePointApp1 on behalf of user)
App-only – must be explicitly requested in the manifest
Apps that do not make OAuth authenticated calls (for example, apps that are only JavaScript running in the app web) cannot use the app-only policy. They can request the permission, but they will not be able to take advantage of it because doing so requires passing an app-only OAuth token. Only apps with web applications running outside of SharePoint can create and pass app-only tokens.In general, a current user is required to be present for a call to be made. In the case of app-only policy, SharePoint creates a SHAREPOINT\APP, similar to the existing SHAREPOINT\SYSTEM user. All app-only requests are made by SHAREPOINT\APP. There is no way to authentication as SHAREPOINT\APP through user-based authentication.
When the app-only policy is used, content database authorization checks only take into account the app identity. In particular, when this policy is used, an authorization check succeeds if the current app has sufficient permissions to perform the action in question, regardless of the permissions of the current user, if any.
Guidelines for using the app-only policy
All OAuth and server-to-server calls should be user + app policy type calls (not app-only policy type), with the following exceptions. OAuth and server-to-server calls should use the app-only policy if:
The app needs to elevate its permissions above the user for a specific call (for example, to approve an expense report under conditions evaluated by the app).
The app is not acting on behalf of any user (for example, the call is being made by the app alone, not by a user who is using the app).
Today will not be an exhaustive treatment of OAuth.
On premises, we have S2S “high trust” apps – certificates/STS
For the apps authenticating with ACS, an access token for SharePoint stays valid for 12 hours once issued, while a refresh token stays valid for six months.
For security reasons, Internet Explorer prevents pages that are on different integrity levels (also known as security zones) to share cookies because each integrity level has its own cookie store. The integrity level of a page is determined by its top-most page, and any frame within that page will share the same integrity level. When the remote app page and SharePoint website are in different security zones, the authorization cookies cannot be sent. If there are no authorization cookies, and the IFrame tries to load the proxy page, it will be redirected to the SharePoint sign-in page. The SharePoint sign-in page cannot be contained in an IFrame for security reasons. In these scenarios, the library cannot load the proxy page, and communication with SharePoint is not possible.
Best practice: Use the apphost pattern
To handle a cross-zone scenario, we recommend that you have an apphost page in SharePoint. The apphost page is a SharePoint page that contains the remote page in an IFrame. Everything inside the IFrame in the apphost page exists in the same security zone as the app web. The cross-domain library in the remote page can receive the authorization cookies and loads the proxy page successfully.
You can use appregnew.aspx to register your app if you are going to use the app only in one tenant. For example, if you're creating apps for a single organization and you're going to use an app only within your corporate catalog, you can use appregnew.aspx to get the client Id. You would not be able to use the app in a multitenant scenario. In particular, the client Id cannot be found when used in the context of tenants other than the one where it was created. You also would not be able to publish your app in the Office Store.
You do not HAVE to have a local dev VM to do app development!
Data can be accessed securely, regardless of whether or not there is a firewall between SharePoint and the external web server