Everybody wants an app or at least they think so, SharePoint 2013 provides an Application Model to handle all your 'appy' desires. Are your current SharePoint 2007 or 2010 solutions considered truly 'self-contained'? Probably not. In this session we will discuss the short comings of older solutions, briefly review the different App Model options and finally walk through the architecture of an existing SharePoint 2013 application. We will help you ignore the hype and spend time understanding the benefits of the App Model as it is crucial for your 2013 strategy.
2. Abstract
Everybody wants an app or at least they think so, SharePoint 2013
provides an Application Model to handle all your 'appy' desires.
Are your current SharePoint 2007 or 2010 solutions considered truly 'self-
contained'? Probably not.
In this session we will discuss the short comings of older solutions, briefly
review the different App Model options and finally walk through the
architecture of an existing SharePoint 2013 application. We will help you
ignore the hype and spend time understanding the benefits of the App
Model as it is crucial for your 2013 strategy.
3. About
Andrew is a SharePoint Architect based in the Los Angeles area.
Andrew graduated from North Central College with a Finance
degree, however his background is predominately ASP.NET web
application development with an emphasis on security. Having seen
the 'light' with SharePoint, his focus has been entirely dedicated to
SharePoint since 2007. Andrew attempts to balance technology and
gadgets with his first love: basketball. When not behind a computer
screen, he can be found at the nearest basketball court.
@sharepointac & @bitterac
The SharePoint Garage
Published author discussing Social Computing with SharePoint 2010
Independently published and highly opinionated with SharePoint 2010
custom form development
Open Source Photo Gallery web part for SharePoint 2010
Open Source Photo Gallery using SharePoint 2013 application model
5. Cloud App Model
Apps for SharePoint are self-contained pieces of functionality that extend
the capabilities of a SharePoint website.
Apps integrate the best of the web and SharePoint; they are
targeted, lightweight, and easy-to-use, and do a great job at solving a
user need.
http://msdn.microsoft.com/en-us/library/fp179930.aspx
6. Hosting Options
Provider-Hosted (your IT teams dedicated server)
Autohosted (Azure Web Sites)
For autohosted apps, SharePoint automatically deploys your app into Windows
Azure Web Sites and SQL Azure, and these apps run in the cloud. For provider-hosted
apps, you or your IT department hosts the app on a dedicated server or third-party
hosting service. These apps run on your server or in the cloud, depending on how
you choose to host your app.
From <http://msdn.microsoft.com/en-us/library/fp179930.aspx>
SharePoint-Hosting
When the app is hosted in SharePoint itself, the code is HTML and JavaScript and is
hosted by SharePoint.
From <http://msdn.microsoft.com/en-us/library/fp179930.aspx>
7. How to Apps work without
codebehinds?
REST, JavaScript, CSOM (client side
object model)
Choose the right API Set in SharePoint 2013
http://msdn.microsoft.com/library/f36645da-
77c5-47f1-a2ca-13d4b62b320d.aspx
9. How to Apps work without
codebehinds?
Getting at List fields
10. Architecture of the deployed app
http://blogs.technet.com/b/mspfe/archi
ve/2013/01/31/configuring-sharepoint-
on-premise-deployments-for-apps.aspx
Your app is no longer just a
webpart, your app is officially a 'self-
contained' solution that the developer
decides how to surface functionality to
the parent web. That is not to say that
you can only interact with your app
through the parent web.
11. Apps for SharePoint user experience
options
http://msdn.microsoft.com/en-us/library/fp179930.aspx
12. UX Design for SharePoint 2013 apps
We recommend that you try to give your apps a SharePoint appearance to the
extent possible, although that is not mandatory and may not always be the
best choice. For more information about the user experience guidelines, see UX
design for apps in SharePoint 2013.
From <http://msdn.microsoft.com/en-us/library/fp179922.aspx#AccessingApp>
13. Storing Data
You can still use SP lists just like you did with your old app.
Not too shabby for an option
30,000,000 items per list
View threshold: 5,000
Wheels fall off the wagon if your SQL DBA walks in the room and wants to use normalized
data structure.
http://technet.microsoft.com/en-us/library/cc262787.aspx#ListLibrary
Get data from remote apps with custom proxy
Get data from remote service using web proxy
Data access options for apps in SP2013
http://msdn.microsoft.com/en-us/library/fp179897.aspx
14. SP2010 Demo
How development was done in the past
Feature development, right? Shake your head yes
1. Add wsp to solution store
2. Deploy solution to either entire farm or to specific web application
3. Either manually activate solution at site collection or site
4. Once it is there, then you can use it.
5. Edit page and drop web part into web part zone
6. Edit web part properties
7. WAIT your developer didn't use feature receivers so you have to…
a. Create lists
b. Create columns
c. Insert data
8. NOW you can use your web part
15. SP2013 Demo
1. Find an app in the store
2. Socially have someone surface an app to you
3. Discover apps through online sources
4. Install the app
5. Small configuration (create a login or minor settings)
6. Use the app
16. SP2013 Demo Continued
Discuss sideloading apps
What is a developer site
What license level
Discuss App Store, setup.
20. Content / Editorial Thank You
The SharePoint Garage
Ken Schaefer @KenSchae
Eric Valentour blog.ericvalentour.com
Rob Toro @sharepointtoro
Instrumental for code reviews of both open source projects
21.
22. Atera Prime K2
Axceler KnowledgeLake
CBT Clips KwizCom
Dell QuickStart
Hershey Technologies Virtualworks
Platinum
& Gold
Sponsors
Silver
Sponsors
Hinweis der Redaktion
Synteractive history
Full page is accessing the app directly from site contents after it was installedPart is really called app parts…these are really just iframes. YuckUI custom actions is just a fancy way of saying putting a button in your host web's ribbon
Full page is accessing the app directly from site contents after it was installedPart is really called app parts…these are really just iframes. YuckUI custom actions is just a fancy way of saying putting a button in your host web's ribbon
Full page is accessing the app directly from site contents after it was installedPart is really called app parts…these are really just iframes. YuckUI custom actions is just a fancy way of saying putting a button in your host web's ribbon
I want a graphic here of what a site is and how the webpart is unknown to the developer as to where it is going to be used and how disconnected it is from the data source. Above all the interaction is fraught with danger because….it relies on humans.
I want a graphic here of what a site is and how the webpart is unknown to the developer as to where it is going to be used and how disconnected it is from the data source. Above all the interaction is fraught with danger because….it relies on humans.
I want a graphic here of what a site is and how the webpart is unknown to the developer as to where it is going to be used and how disconnected it is from the data source. Above all the interaction is fraught with danger because….it relies on humans.
I want a graphic here of what a site is and how the webpart is unknown to the developer as to where it is going to be used and how disconnected it is from the data source. Above all the interaction is fraught with danger because….it relies on humans.
I want a graphic here of what a site is and how the webpart is unknown to the developer as to where it is going to be used and how disconnected it is from the data source. Above all the interaction is fraught with danger because….it relies on humans.
I want a graphic here of what a site is and how the webpart is unknown to the developer as to where it is going to be used and how disconnected it is from the data source. Above all the interaction is fraught with danger because….it relies on humans.