• Like
SharePoint 2013 Apps: A Comparison to SharePoint 2010 Web Parts
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

SharePoint 2013 Apps: A Comparison to SharePoint 2010 Web Parts

  • 2,058 views
Published

In this session, I will show two code examples. The first will be of a web part in SharePoint 2010. The next code example will be a SharePoint 2013 provider-hosted app that is implementing the exact …

In this session, I will show two code examples. The first will be of a web part in SharePoint 2010. The next code example will be a SharePoint 2013 provider-hosted app that is implementing the exact same functionality as the SharePoint 2010 web part. This talk will highlight the differences between the two models, and will focus on the how and why of the new SharePoint 2013 app model.

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,058
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
21
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

Transcript

  • 1. SharePoint 2013 Apps: A Comparison toSharePoint 2010 Web PartsTim McCarthySenior Solutions Architect
  • 2. Agenda• Overview• Review of “old school” web parts• The new App model• Pros and Cons of Apps vs. “old school” webparts• Summary/Call to Action
  • 3. Overview• Why this presentation?• Why should I care about Apps?• Why is SharePoint/Office 365 important to adeveloper?
  • 4. Demo: “Old School” Web Part
  • 5. The New App Model• Apps are framed in web sites with SharePointtokens injected via querystring• Code runs outside of the SharePoint farm• Apps can be published to Microsoft’s publicSharePoint store or hosted in a private store
  • 6. Demo: SharePoint App
  • 7. Apps vs. “Old School Web Parts” Pros• Can still use the full power of SharePoint(lists, document libraries, workflows, eventreceivers, BCS, etc.)• No need for network operations team fordeployments• Won’t bring down the farm since the codedoes not run on the SharePoint server(s)
  • 8. Apps vs. “Old School Web Parts” Pros• If using Office 365, can develop on a "regular"machine instead of a 50GB VM!• Can use ASP.NET Web Forms, ASP.NETMVC, PHP, etc.• Remote web site can live anywhere: on-premises, Azure, AWS, etc.
  • 9. Demo: SharePoint App
  • 10. Apps vs. “Old School Web Parts” Cons• Certain parts of object model are restricted(anything targeted at the web applicationlevel)• All calls back to SharePoint are remote webservice or WebDAV calls
  • 11. Summary/Call to Action• The App model is cool and here to stay, getused to it• Why should I care about Apps?• Get an Office 365 developer subscription
  • 12. Source Code
  • 13. Thank you for your timeand attention today.Please visit us at Perficient.com