Goals Foundation session to cover off on the fundamentals Understand what it takes to get started with SharePoint development.

Download Report

Transcript Goals Foundation session to cover off on the fundamentals Understand what it takes to get started with SharePoint development.

Goals
Foundation session to cover off on the fundamentals
Understand what it takes to get started with
SharePoint development
Agenda
Fundamentals
Developer Tools
Programmability
Common Tasks
Where to Next?
What is SharePoint?
For more: http://sps.cloudapp.net/
SharePoint
SharePoint Architecture
SharePoint
Visual Studio
Napa
SPD
Development
Apps
Events
…
Sites
Security
…
Content
Services
Content DB
ASP.NET/IIS
Windows OS
Azure
Web
…
Deployment
SharePoint Farm Topology
SharePoint**
Web Front End
App Servers
development
Content DB
For more: http://technet.microsoft.com/en-us/library/cc263199.aspx
**Small to medium farm
deployment
What is SharePoint Development?
Can be defined along a spectrum
Simple browser-based configuration/development
Client-side programming/scripting (e.g. HTML, JS, CSS)
Branding (e.g. Master Pages)
Managed code development (e.g. ASP.NET, C#/VB)
My preferred segmentation
API/OM
Developer
Master Page/CSS
Designer
UI Config./HTML
Power User
Site/App/List/Item
End User
http://msdn.blogs.com/steve_fox
Site creation and
administration
Themes, branding and
master pages
HTML content editing
Inline JavaScript
CSS Overrides
Browser-based
Lightweight, client apps
SharePoint or Office Apps
Quick run and deploy
Migrate to Visual Studio
Free “App”
Designer tool
Create, edit and view
capabilities
Not meant to integrate
with ALM
Migrate to Visual
Studio
Free tool
Fully featured IDE
SharePoint project and
item-level templates
Supports source code
ALM
Build and retract
Remote debug and deploy
Not free, but there is a trial
period
Branding
Debugging
Community & ISV
…
http://visualstudiogallery.msdn.microsoft.com/
When looking to extend SharePoint, you need to consider all
options from farm solutions, sandboxed solutions to different
types of apps. This is true across the product… many times
you have lots of options on who to achieve something, but
no “best” option. The best you can do is to make sure you are
well educated and prepared for all options so you can make
the most informed decision possible.
http://www.andrewconnell.com/blog/
Programming Against SharePoint
Services
SharePoint Server Object Model
Client-side Object Model
REST/Odata (_API)
Client-side Script/Mark-up
PowerShell
Deployment
Code/Packaging
Inline Code
SharePoint App (.APP)
Windows SharePoint Solution (.WSP)
SharePoint Feature
Marketplace
Corporate Catalog
Office Store
Unlike Web Parts, App Parts were
not designed to participate in App
Part to App Part communication.
SharePoint 2013 just adds OAuth support to
authenticate SharePoint apps, it does not use
OAuth to authenticate users. However, when
using OAuth from a SharePoint app, you can
also check a user’s permissions (perform
authorization).
http://toddbaginski.com/blog/
Common Tasks
Creating, administering a site
Creating a Web part
Data (e.g. List) Programming
SharePoint-Hosted App
Content types, site columns, etc.
Branding & Theming
The “tip” I most frequently use is getting the
list through the URL instead of the title. It’s a
pain to get right the first time but once you do
it you’ve got a stable way to access a list (since
title can change) and it’s more performant
since SharePoint doesn’t have to load the
collection of lists up. However, it’s not
supported in the CSOM or REST (without a
second call)
http://thorprojects.com/blog/default.aspx
Sampling of Interesting SPC Dev Sessions
Get started…
Got to http://dev.office.com
And look out for….
MySPC
http://myspc.sharepointconference.com