Your SlideShare is downloading. ×
0
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

From Trashy to Classy: How The SharePoint 2013 App Model Changes Everything

6,439

Published on

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 …

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.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
6,439
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 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.
  • Transcript

    • 1. SharePoint 2013 AppsFROM TRASHY TO CLASSY, HOW THE SP2013 APP MODEL CHANGESEVERYTHING
    • 2. Abstract Everybody wants an app or at least they think so, SharePoint 2013provides 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, brieflyreview the different App Model options and finally walk through thearchitecture of an existing SharePoint 2013 application. We will help youignore the hype and spend time understanding the benefits of the AppModel 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 Financedegree, however his background is predominately ASP.NET webapplication development with an emphasis on security. Having seenthe light with SharePoint, his focus has been entirely dedicated toSharePoint since 2007. Andrew attempts to balance technology andgadgets with his first love: basketball. When not behind a computerscreen, 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 2010custom form development Open Source Photo Gallery web part for SharePoint 2010 Open Source Photo Gallery using SharePoint 2013 application model
    • 4. 2008-2009 2010 2011 2012Synteractive, who we are
    • 5. Cloud App Model Apps for SharePoint are self-contained pieces of functionality that extendthe capabilities of a SharePoint website. Apps integrate the best of the web and SharePoint; they aretargeted, lightweight, and easy-to-use, and do a great job at solving auser 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 WindowsAzure Web Sites and SQL Azure, and these apps run in the cloud. For provider-hostedapps, you or your IT department hosts the app on a dedicated server or third-partyhosting service. These apps run on your server or in the cloud, depending on howyou 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 ishosted by SharePoint. From <http://msdn.microsoft.com/en-us/library/fp179930.aspx>
    • 7. How to Apps work withoutcodebehinds? REST, JavaScript, CSOM (client sideobject model)Choose the right API Set in SharePoint 2013http://msdn.microsoft.com/library/f36645da-77c5-47f1-a2ca-13d4b62b320d.aspx
    • 8. How to Apps work withoutcodebehinds? REST
    • 9. How to Apps work withoutcodebehinds? Getting at List fields
    • 10. Architecture of the deployed app http://blogs.technet.com/b/mspfe/archive/2013/01/31/configuring-sharepoint-on-premise-deployments-for-apps.aspx Your app is no longer just awebpart, your app is officially a self-contained solution that the developerdecides how to surface functionality tothe parent web. That is not to say thatyou can only interact with your appthrough the parent web.
    • 11. Apps for SharePoint user experienceoptionshttp://msdn.microsoft.com/en-us/library/fp179930.aspx
    • 12. UX Design for SharePoint 2013 appsWe recommend that you try to give your apps a SharePoint appearance to theextent possible, although that is not mandatory and may not always be thebest choice. For more information about the user experience guidelines, see UXdesign for apps in SharePoint 2013.From <http://msdn.microsoft.com/en-us/library/fp179922.aspx#AccessingApp>
    • 13. Storing DataYou can still use SP lists just like you did with your old app.Not too shabby for an option30,000,000 items per listView threshold: 5,000Wheels fall off the wagon if your SQL DBA walks in the room and wants to use normalizeddata structure.http://technet.microsoft.com/en-us/library/cc262787.aspx#ListLibraryGet data from remote apps with custom proxyGet data from remote service using web proxyData access options for apps in SP2013http://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 didnt 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.
    • 17. SP2013 Demo Continued
    • 18. SP2013 Demo Continued
    • 19. SP2013 Demo Continued
    • 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. Atera Prime K2Axceler KnowledgeLakeCBT Clips KwizComDell QuickStartHershey Technologies VirtualworksPlatinum& GoldSponsorsSilverSponsors

    ×