For years, packaging has been an essential best practice to manage the deployment of custom apps across dev, test and production environments. While this principle remains, complexity has grown with the cloud and the latest generation of SharePoint applications. Beyond simple SharePoint solution packages (WSPs)—SharePoint apps have evolved into a conglomeration of code that can be deployed into Windows Azure, SQL Azure, SharePoint Online, not to mention online markets such as SharePoint Store. Join us to gain a solid footing in this new application landscape. Are you prepared to deploy and manage the next generation of custom apps? If not, invest 60 minutes in your career to get up to speed.

1. Deploying and
Managing SP2013
Apps
Randy Williams
Director of AvePoint Client Services

2. Randy Williams
Director of ACSAuthor

3. Why do we need
a new app model

4. Challenges with WSP solutions
 Full-trust solutions
 Sandboxed solutions
 Requires administrative deployment and support
 Lifecycle management
 Steep learning curve

5. Benefits of the new app model
• Lower learning curve – re-use your existing web
technology background
• SharePoint Store opens up new revenue potential
Developers
IT Managers
• Apps decoupled from SharePoint – simplifies upgrades
• Virtually no risk to farm
• Corporate catalog facilitates governance controls
Info Workers
• Based on a proven and familiar app model
• Apps can be found in SharePoint Store or a corporate
app catalog
• Can provision, upgrade and delete

6. A small, easy-to-use, stand-
alone productivity app that
solves a specific end-user
need.
What is a SharePoint 2013 App?

7. Demo
Built-in Apps

8. So - what exactly is an app?
 Can contain some declarative SharePoint artifacts
 External app provides SharePoint UI through IFrame
 External app uses CSOM or REST (OData) to call back
 No custom server-side code running on SharePoint WFEs
An application whose interface is
surfaced through SharePoint but code
is executed elsewhere

9. How apps run

10. Apps vs solution packages
Apps Sandboxed WSP Full trust WSP
Where does server-side code run?
Anywhere but
farm
Farm (User Code
Service)
Farm (w3wp.exe)
Scalable Highly Limited Based on farm
Who installs and removes Users
Site collection
admin
Farm admin
Supported in SP2013 Yes Yes Yes
SharePoint Online compatible Yes Yes No
Azure-hosting compatible Yes No No
Requires local farm for development No Yes Yes
Remote deployment and debugging
from Visual Studio
Yes No No
Package extension and type .app (zip file) .wsp (cab file) .wsp (cab file)

11. Application lifecycle
 Apps are designed to be user
provisioned
 Users find and provision apps from
App Catalog or SharePoint Store
 App owners can also upgrade
and uninstall

12. Three hosting options

13. Three hosting options

14. Three hosting options

15. Three hosting options

16. Host web and app web
 The host web is where app is added, removed, upgraded
 If app has SharePoint artifacts, a sub-web is created underneath
the host web
 This sub-web is called the app web
 App web is only accessible using isolated domain name
http://app-
af48d482118ab1.contosoapps.com/myapp

17. App web
 Provisioned by host web
 Contains only web-scoped features
 Initial UI is immersive, full page
 Custom master page is assigned (app.master)
 Quick launch and common layout pages are unavailable
 Only declarative code allowed within the app web

18. Deploying apps in SharePoint Online
 Environment is pre-configured to support 2013 apps
 All hosting options are available
 Windows Azure for any server-side custom code (PHP, .NET)
 SQL Azure for any database requirements
 Create App Catalog to host corporate-approved apps
 SharePoint Store cannot be hidden, but you can prevent apps
from being installed

19. Deploying apps within SP 2013 farms *
 Environment is not pre-configured (details covered later)
 All app hosting types are supported
 App catalog owners can upload .app packages directly
 App catalog owners can also approve requested apps
 SharePoint Store behavior is the same as with SPOL
* On-premises or IAAS-hosted farms

20. Demo
.app package

21. Configure a farm to support 2013 apps
 Create DNS zone for app domain name (e.g. contosoapps.com)
 Create wildcard DNS CNAME entry and point to WFE/load
balancer
 Obtain a wildcard SSL cert
 (PowerShell) Create a Subscription Settings service application
and proxy
 (PowerShell or CA) Create an App Management service
application
 For details: http://technet.microsoft.com/en-

22. Demo
Managing apps

23. randy.williams@avepoint.com @tweetraw
Thank you

25. Atera Prime K2
Axceler KnowledgeLake
CBT Clips KwizCom
Dell QuickStart
Hershey Technologies Virtualworks
Platinum
& Gold
Sponsors
Silver
Sponsors