• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Apps for SharePoint 2013
 

Apps for SharePoint 2013

on

  • 2,849 views

A short introduction to the new app model in SharePoint 2013

A short introduction to the new app model in SharePoint 2013

Statistics

Views

Total Views
2,849
Views on SlideShare
2,849
Embed Views
0

Actions

Likes
1
Downloads
0
Comments
1

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Updated to include links to relevant Microsoft resources.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Apps for SharePoint 2013 Apps for SharePoint 2013 Presentation Transcript

    • Apps for SharePoint 2013 Alex Pop July 2013
    • Application development models in SharePoint 2010 ● sandboxed solutions: ○ limited server side API access; ● farm solutions: ○ installed using "*.wsp" packages that have impact on the whole SharePoint farm when installed or updated ○ on a production system these solutions have to be installed out of hours;
    • Application development models in SharePoint 2013 ● sandboxed solutions: deprecated; ● farm solutions: only use for applications targeted at SharePoint administrators; ● new "apps for SharePoint" model: ○ THE recommended model for end user applications; ○ derived from SharePoint Online and Office 365 requirements; ○ isolates all custom server-side code from the SharePoint instance
    • "Apps for SharePoint" types ● There are 3 new types of SharePoint solutions: ○ SharePoint hosted, autohosted and provider hosted; ○ they all create a new ".app" file that has to be deployed to SharePoint using a very complex process; ● SharePoint hosted app: a SharePoint app project containing SharePoint assets(lists, workflows, etc.) + web pages that can only use client side code;
    • "Apps for SharePoint" types(cont.) ● Autohosted and Provider hosted apps: ○ both have a SharePoint app project and an ASP. NET web project: a SharePoint app and a web application; ○ the Autohosted solution packages all assets (including the website and the database scripts) in the ".app" file; ○ the Provider hosted solution packages only the SharePoint app project into the ".app" file. The web application deployment is done independently.
    • Provided hosted apps - integration ● the web application communicates with SharePoint using: ○ a shared security certificate; ○ a helper library "AppForSharePointWebToolkit" (available as a NuGet package); ○ the SharePoint Client Object Model(CSOM); ○ the SharePoint app manifest needs to list the SharePoint permissions that your app needs;
    • Provided hosted apps - integration (cont.) ● the web application can expose "app parts" to SharePoint: <iframe> elements that render content from the web application; ● the SharePoint app can: ○ package SharePoint assets(lists, content types, workflows, etc.); ○ extend SharePoint menus;
    • What this all means ● employ modern web development practices: develop clean, testable applications; ● leverage existing web development skills: you don't need advanced SharePoint knowledge to accomplish even the most basic tasks; ● scalable, distributed web applications: you can allocate more resources to an app for SharePoint if and when needed; ● support for other application frameworks?
    • Scenarios enabled by Apps For SharePoint ● use SharePoint as a data store together with a custom web application; ● use a third party data store together with a custom web application; ● mix and match SharePoint and external data stores; ● provide "app parts" to SharePoint;
    • Current SharePoint application architecture ● the entry point for all applications is a SharePoint page; ● the SharePoint app delivers all SharePoint specific assets; ● the web application will render all UI components; ● the web application will interact with Sharepoint using the current user identity or using a custom identity within a scheduled job;
    • Development update ● Bootstrap is everywhere: ○ Bootstrap master pages now deployed on the SharePoint server; ○ Bootstrap is used to style the app for SharePoint; ○ The result is consistent styles applied throughout; ● ASP.NET MVC: ○ provides Windows authentication and session identity; ○ builds the single page application skeleton; ○ minifies and concatenates all assets;
    • Development update (cont.) ● ServiceStack: used to build RESTful , testable web services (90% server side code coverage with AutoFixture); ● AngularJS: ○ MV* framework for single page applications; ○ reusable web components(a.k.a the future of web); ○ testable code via dependency injection; ● Kendo UI Web: powerful grid and other widgets plus IE8 support (now compatible with AngularJS); ● Entity Framework 5: using the code first model with database migrations.
    • Notes ● Reimagine SharePoint Development: http: //msdn.microsoft.com/en- US/office/apps/dn133840 ● Deciding between apps for SharePoint and SharePoint solutions: http://msdn.microsoft. com/library/sharepoint/dn268593(v=office. 15)