The document discusses developing apps for SharePoint 2013. It provides an agenda for a session that will cover setting up a development environment, using apps, the new app model, building a first app, choosing an API, and packaging/publishing apps. It also provides background on how apps came to be for SharePoint, describing them as isolated custom components with access control that provide a familiar user experience and can be distributed through an app store.
4. Email : uaespug@live.com
Website : uaesharepoint.org
January, 2013
Online and in class sessions
20 Organizers, Speaker and Contributor
Around 500 social media followers
Register Microsoft technical Community
Facebook: http://www.facebook.com/UAESharepoint
Twitter : @UAESharePoint
YouTube: http://www.youtube.com/UAESharePoint
LinkedIn: linkedin.com/groups/UAESharePoint-4759377n
15. Let’s make SP custom components as mobile
apps:
Wide Developers Platforms
Isolated
Process
Access Control
Components
Familiar user experience
App store
Apps are mini applications that extend what you can do with the SharePoint 2013 Sites.
Go to Site contentAdd an App form Apps Store
Next slide we are going to address challenges in old SharePoint custom solutions (*.WSP)The sandboxed solutions run in an environment that has access to a subset of the SharePoint Foundation server object model and a subset of the Microsoft .NET Framework 3.5 assemblies. Code in a sandboxed solution must also run under a significantly restricted Code Access Security (CAS) policy.
The first problem with SharePoint solutions development is that most of the custom code written bydevelopers runs inside the SharePoint host environment.Farm-Trust Solutions:Not isolated and can cause a lot of issue for the ISS worker processUse server resource and this cause issues with performanceCan access physical resources and other SharePoint site collections with no access controlCause exceptions on the web sites.Down timeAs developer,The difficulty in obtaining the developer environment Update and upgradeSandbox solution have the same issues with a small enhancementsHowever, this simply replaces one problem with another.
What is an app ( The story )?
Microsoft SharePoint Product Team chat about SharePoint future
Let’s make SP custom components as mobile apps:Wide Developers PlatformsIsolated: Process, Access Control, ComponentsFamiliar user experience App store
Custom logic in apps for SharePoint is always distributed "down" to the client or "up" to the cloud (or "over" to some server outside the SharePoint farm).
Custom logic in apps for SharePoint is always distributed "down" to the client or "up" to the cloud (or "over" to some server outside the SharePoint farm).
Create App using Visual StudioNavigate the FilesGo to default page and App.js then descript the codeDeployTake about manifest file Add List ( Clients Says testimonials)Add Customers to default pagedeploy again
Full Page: RequiredApp Parts and Custom Actions: OptionalCustom Action also known as “UI command extensions”
Add and App part Deploy (RUN the project)Add some code (read latest customer Items)Make change and Save
SharePoint-Hosted app (Provisions an isolated sub web on a host web)Use SP artifacts Use HTML & JavaScript for UI & client-side logicUse Workflows for middle tier logicCloud-hosted appsUse server codeReceive SP eventsUse OAuth to access SP
Choose the right API set in SP 15:http://msdn.microsoft.com/en-us/library/sharepoint/jj164060.aspx
Packaging & Publishing
Create App catalogAdd the app to the team site Test it