1. SharePoint Online – Developing Solutions for the Cloud Chris Mayo Microsoft Corporation http://blogs.msdn.com/cmayo
2.
3.
4. SharePoint 2010 Administration Server Farm Web Application Site Collection Sites Web Application Web Application Web Application … Site Collection Site Collection … Sites Lists Libraries Lists Libraries Sites
5. SharePoint Online Administration SharePoint Online Tenancy Site Collection Sites Site Collection Site Collection … Sites Lists Libraries Lists Libraries Sites
10. Sandboxed Solutions Support Item Template Sandbox Compatible? Visual Web Part No Visual Web Part (Sandboxed) Yes Web Part Yes Sequential Workflow No State Machine Workflow No Business Data Connectivity Model No Application Page No Event Receiver Yes Module Yes Content Type Yes List Definition From Content Type Yes List Definition Yes List Instance Yes Empty Element Yes User Control No
Where is SPO the same as SP2010 dev? Where is SPO different from SP2010 dev? Overview Understand all the concepts Drill deeper via future webcasts. Demo Prep: Remove solutions from Site Collection on-prem and in SPO. Turn off Publishing in Site Collection on prem and in SPO. Delete Purchasing site on-prem and in SPO. Create Purchasing site on-prem and in SPO. Turn on Publishing in Site Collection on prem and in SPO. Turn on Publishing in Purchasing Site on prem and in SPO.
A SharePoint solution has two sides to it. The declarative CAML used to create many components such as list templates and content-types, and The code side in workflow, event receivers or Web Parts. Sandboxed solutions can contain all these elements. The solutions are deployed to a special gallery which sits under _catalog like the other built-in galleries. Execute in a partially trusted environment Code executes in a special service process Subject to CAS Validation framework Provides way to do custom farm wide validation for the deployed packages Each solution is isolated to its site collection MS Confidential : SharePoint 2010 Developer Workshop (Beta1) Lecture 13: Sandboxed Solutions -
Code components: Feature receivers Event receivers SPItemEventReceiver SPListEventReceiver SPWebEventReceiver Navigation Web Parts (if derived from the WebPart class) Microsoft InfoPath forms logic SharePoint Designer workflow activities Sandboxed solutions workflow activities Declarative components: Declarative workflows Content types, site columns Lists and list definitions Visual and nonvisual Web Parts Custom actions, ribbon extensions Client-side technologies Web templates, site pages, page layouts, and master pages The following capabilities and elements are not supported in sandboxed solutions: Access to the Internet to make web service calls Access to a hard disk to read or write files You can, of course, read and write to lists and libraries within SharePoint Online. Web application-scoped or farm-scoped Features Adding assemblies to the global assembly cache Running security-related functionality; for example, RunWithElevatedPrivileges or other SPSecurity methods Custom Action groups HideCustomAction element Content type binding Web Part connections MS Confidential : SharePoint 2010 Developer Workshop (Beta1) Lecture 13: Sandboxed Solutions -
Throughout each SharePoint release, Microsoft receives more and more requests for new Web Services Instead of continuously building new Web services (and replacing existing ASMX services with WCF services), they now provide a client object model The client object model provides an abstraction layer so process off the SharePoint server can interact with SharePoint using a consistent API that is very closely matched to the familiar server API MS Confidential : SharePoint 2010 Developer Workshop (Beta1)
![[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Agenda](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)