New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
Come riprogettare le attuali farm solution di share point con il nuovo modello di app
1. OFF002 -Come riprogettare le attuali Farm Solution di SharePoint con il nuovo modello di App
Fabio Franzini –SharePoint MVP
2. •SharePoint MVP
•Senior Consultant and Software Engineer
•MCT Trainer
•MCPD Web Applications, MCTS SharePoint 2010/2007
•Official Ignite Trainer for SharePoint 2013 & 2010 in Italy
•Over 10 years experience in IT as a software engineer
•Twitter: @franzinifabio
•Email: fabio@fabiofranzini.com
•Web: www.fabiofranzini.com
About Me
3. “SharePoint 2013 App Model Succinctly”
SharePoint2013 App Model Succinctly is a hands-on approach to learning how to develop SharePoint apps.
Author Fabio Franzini introduces readers to the concepts that make SharePoint 2013 simpler and easier to use than previous development models.
You’ll learn to develop both on-premises and cloud applications in Visual Studio 2013, then enable your apps to communicate with SharePoint using the client-side object model (CSOM) or the representational state transfer (REST) API
http://bit.ly/1ytzthl
4. Agenda
•Evolution in SharePoint Development
•SharePoint Remote API Intro
•CSOM / REST
•Convert WSP to APP
5. SP2007WSP
SP2010WSP
SP2013
App
Declar. App &
Workflow Events
CSOM
_api
_api
Evolution in SharePoint Development
CSOM
6. New App Model
•Apps no longer live in SharePoint
•Reduces the ramp-up time for those building apps (Don’t need to know/be as familiar with SharePoint “-isms”)
•Custom code executes in the client, cloud or on-premise
•Easier to upgrade to future versions of SharePoint
•Works in hosted environments w/o limitations
•Apps communicate with SharePoint via REST / CSOM
•Apps are granted permissions to SharePoint via OAuth
•Acquire apps via centralized Marketplace
•Some Examples http://code.msdn.microsoft.com/officeapps
7. Kindsof Apps
Provision an Isolated sub web on a parent web
Reuse web elements (lists, files, out-of-box web parts)
No server code allowed; use client JavaScript for logic, UX
Server side code allowed
Any web stack allowed
Windows Azure + SQL Azure provisioned invisibly as apps are installed
8. JavaScript Library
Silverlight Library
.NetCLR Library
Custom Client Code
Client
Server
_apiis new alias for_vti_bin/client.svc
SharePoint 2013 Remote API
ODataExecute Query
9. Programming using CSOM Client.svcServer OMContentdatabaseJavaScript OMProxyManaged OMProxy
Your C# and VB.NET Code
Your JavaScript Code
XML Request
XML Request
JSON Response
JSON Response
Browser
Managed Client
SharePoint Web Server
12. REST URLs in SharePoint 2013
•CSOM URLS can go through _apifolder
•Simplifies URLs that need to be built
•Removes client.svc file name from URL
•You can replace this URL
http://contososerver/_vti_bin/client.svc/web
•With this URL
http://contososerver/_api/web
16. Office 365 «LIMITATIONS»
•FARM SOLUTIONS: NO!
•No server-side object model
•No feature receivers
•No timer jobs
•No event receivers
•No custom fields
•No site definitions
•No custom web parts
•SANDBOX SOLUTIONS: YES, partially …
•We cannot use code in Sandbox solutions
•APPS: YES!
•This is the suggested model
17. Convert WSP to APP
Farmsolutionartifacts
App model/remote code artifacts
Web parts
App parts
Eventreceivers
Remoteeventreceivers
Application pages
Pagesin Provider-HostedApps
Site definitions
Web templatesin SandboxSolutions
Customfields
Client SideRenderingtemplates
Custom usercontrols
App parts, Javascript in page
Custom ribboncontrols/custom actions
The same, butwith Appspages/Javascript scripts
Timer jobs
Scheduledprocessesin Azure
Brandingsolutions
The same, butwithoutserver-side code
Featurereceivers
AppEvents
Workflows
Declarativeworkflowsin Apps
Custom authentication
NOTHING
Runwith elevatedprivileges
App-onlyauthentication
Powershellscripts
Powershellscripts with CSOM