49 151 52 602 822
•
2 likes•791 views
Explain and Explore SharePoint 2013 - Cologne and Munich, September 2013
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to 49 151 52 602 822
Similar to 49 151 52 602 822 (20)
More from Adis Jugo
More from Adis Jugo (20)
Recently uploaded
Recently uploaded (20)
49 151 52 602 822
- 2. SharePoint and client-side development Solution types and development techniques SharePoint APPs architecture
- 3. some background A TURBULENT HISTORY OF SHAREPOINT SOLUTIONS DEVELOPMENT
- 4. questions
- 6. BL Classes not SPContext Aware SPContext Transport/Creation? SPContext Aware Infrastructure Layer Classes Dependency injection
- 7. problems • Migration • Not possible with Office 365 (or any other hosted services)
- 8. enterprise Architectural considerations Quality Attributes Impersonation Security Logging Performance Caching Concurrency Testing Localization / Internationalization Deployment Configuration Flexibility / Future Proof Cloud-enabled
- 10. deprecated
- 11. sandbox Architectural considerations Quality Attributes Impersonation Security Logging Performance Caching Concurrency Testing Localization / Internationalization Deployment Configuration Flexibility / Future Proof Cloud-enabled
- 12. client solutions AS OF SHAREPOINT 2003
- 13. ASMX WEB SERVICES (SOAP)
- 14. No SPContext Some aware Web Service Components
- 15. external Architectural considerations Quality Attributes Impersonation Security Logging Performance Caching Concurrency Testing Localization / Internationalization Deployment Configuration Flexibility / Future Proof Cloud-enabled
- 16. limitations • Suitable for integrating other solutions with SharePoint
- 17. ASMX WEB SERVICES (SOAP) ASMX WEB SERVICES (SOAP)
- 18. types 1 2 3 Enterprise/Farm solutions Sandbox SP Apps Full trust solutions Declarative elements New Apps model Customizations to file system of Partially trusted code service Deployed from corporate servers still included for limited catalog or office market place server side support Classic model from 2007 Manage permission and licenses specifically Preferred option
- 19. sharepoint apps SOLE CLIENT-DEVELOPMENT BASED SOLUTIONS FOR SHAREPOINT SERVER 2013
- 21. why safe! • Cloud ready!
- 22. app design Provider-Hosted App SharePoint “Bring your own server hosting infrastructure” Your Hosted Site Cloud-based Apps Web Developers will need to isolate tenants Get remote events from SharePoint Use CSOM/REST + Azure Auto-Provisioned App OAuth to work with SP Azure Windows Azure + SQL Azure provisioned SharePoint Web (from WebDeploy, invisibly as apps are installed DacPac) SharePoint-hosted App Parent Provision an isolated sub web on a parent Web web • Reuse web elements App Web (lists, files, out-of-box web parts) • No server code allowed; use client (from WSP) JavaScript for logic, UX
- 23. hosted DATABASES REST, CSOM SERVICES APP DATA
- 24. azure SQL AZURE REST, CSOM SERVICES APP DATA
- 25. apps and trust main SharePoint site app1 SharePoint site http://intranet.contoso.com http:// tenant-apphash1.contosoapps.com /sites/web/appguid http://apps-87e90ada14c175.contosoapps.com/sites/web/014c9c59-5d9c-4a59-a5ce-2116a4c90296
- 27. marketplace 2 3 SP Platform App Submission 4 6 1 5
- 28. upgrade process animated
- 29. what and when
- 31. contact Adis Jugo Technology Advisor (Aalen – Munich – Cologne – Frankfurt – Sofia – Sarajevo) M.DE +49 151 52 602 822 Mail: adis.jugo@plan-b-gmbh.com Blog: adisjugo.com Twitter: @adisjugo