Building SharePoint 2013 Sandboxed Solutions And Apps Agenda Development in Visual Studio with/without SharePoint 2013 Logging Cross-site collection JavaScript Apps that do not require permissions to a SharePoint site Lists, content types, page layouts deployed to SharePoint site Web parts and custom site templates .wsp package + .app package Separation of code (JavaScript) and XML definitions Fast re-deployment of code, while the lists and content types stay

1. Building Sandboxed
Solutions with Apps
#spsoslo
Sonja Madsen
May 31st, 2014

2. Sonja Madsen
SONJASAPPS
Freelance Developer/Architect/Consultant
Over 10 years with SharePoint
SharePoint MVP
Speaker
Microsoft partner and vendor
@sonjamadsen
dev@sonjasapps.com
Sp2013.blogspot.com

4. Agenda
Development in Visual Studio without SharePoint 2013
Logging
Cross-site collection JavaScript
Apps that do not require permissions to a SharePoint site
Lists, content types, page layouts deployed to SharePoint site
.wsp package + .app package
Separation of code (JavaScript) and XML definitions
Fast re-deployment of code, while the lists and content types stay

5. Microsoft about
Sandboxed
solutions
All future investments will go to making the new SharePoint app model richer
and more powerful. Accordingly, we recommend that all new development
should use the new app model whenever possible.

6. Sandboxed
solutions in
SharePoint 2013
We have apps, but we yet bother with sandboxed solutions
stmentsw go to making the new SharePoint app model richer and more
powerful. Accordingly, we recommend that all new development should use the
new app model whenever possible.
SharePoint dev blog
The official Microsoft blog for SharePoint developers

7. Apps
.app package deployed/uploaded to App Catalog
Apps are software that run as advanced IFRAME on a SharePoint site
Apps require permissions to SharePoint host web
SharePoint hosted apps (JavaScript)
Cloud apps (C#)
Apps provide logging
Apps are not a Ferrari
Lists, pages, and content types are NOT deployed to SharePoint
End-users can’t customize app pages

8. Sandboxed
solutions
.wsp package deployed/uploaded to solution gallery
Only declarative XML and no-code solutions
Lists, pages, and content types ARE deployed to SharePoint
End-users CAN customize pages

9. Development
Sandboxed solution in Visual Studio require SharePoint on-premise
Apps in Visual Studio require a SharePoint site (on-premise or Office 365)
SharePoint on-premise (version 15) and Office 365 (version 16)

10. Pizzamuffin

11. (Sand)boxed
apps
Focus on the task at hand
Use the best of two worlds

12. DEMO Project

13. SharePoint
SharePoint is perfect for this – project sites, teams, collaboration

14. SharePoint out-
of-box
SharePoint: No project metadata, no overview
No governance on how to call sites, where to create sites, permissions
How to find ”my project sites"
Look and feel, site templates?
Apps: we can do metadata and overview, but no project sites

15. Solution
Custom content type and site columns
Custom list with custom list form
Code that creates sites
Overview page
Site template (standard team or project site)

16. DEMO

17. DEMO

18. The best of two
worlds
Development in Visual Studio without SharePoint 2013
Logging
Cross-site collection JavaScript
Apps that do not require permissions to a SharePoint site
Lists, content types, page layouts deployed to SharePoint site
.wsp package + .app package
Separation of code (JavaScript) and XML definitions
Fast re-deployment of code, while the lists and content types stay

19. Platinum
SharePint
Raffle
Platinum
Gold