SharePoint 2013 Apps: A Comparison to SharePoint 2010 Web Parts
Tim McCarthy
Senior Solutions Architect
Agenda• Overview• Review of “old school” web parts• The new App model• Pros and Cons of Apps vs. “old school” web
parts• Summary/Call to Action
Overview• Why this presentation?• Why should I care about Apps?• Why is SharePoint/Office 365 important to a
developer?
Demo: “Old School” Web Part
The New App Model• Apps are framed in web sites with SharePoint
tokens injected via querystring• Code runs outside of the SharePoint farm• Apps can be published to Microsoft’s public
SharePoint store or hosted in a private store
Demo: SharePoint App
Apps vs. “Old School Web Parts” Pros• Can still use the full power of SharePoint (lists,
document libraries, workflows, event receivers, BCS, etc.)
• No need for network operations team for deployments
• Won’t bring down the farm since the code does not run on the SharePoint server(s)
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.NET MVC,
PHP, etc.• Remote web site can live anywhere: on-
premises, Azure, AWS, etc.
Demo: SharePoint App
Apps vs. “Old School Web Parts” Cons• Certain parts of object model are restricted
(anything targeted at the web application level)
• All calls back to SharePoint are remote web service or WebDAV calls
Summary/Call to Action• The App model is cool and here to stay, get
used to it• Why should I care about Apps?• Get an Office 365 developer subscription
Thank you for your timeand attention today.
Please visit us at Perficient.com
Recommended
