Getting started with Office 365 SharePoint 2010 online development

Getting started with SharePoint 2010 Online development

Jeremy ThakeChief Architect, AvePoint Inc.

© 2012 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.

SpeakerAuthor

AvePoint Labs

Chief ArchitectText/Icon/Pic

Jeremy Thake

jthakejeremy.thake@avepoint.com

Agenda

• Application Development Platform• Getting Started • Sandboxed Solutions• Application Lifecycle Management • Migrating Apps

APPLICATION DEVELOPMENT PLATFORM

Building Blocks

• Authentication & Authorization• Customization & Personalization• Branding• Disaster recovery• Availability• Site collections & Sub sites

No more…

• installing SQL• configuring IIS• deploying components to server• writing service level agreements• writing disaster recovery plans

List Building Blocks

• Attachments• Metadata• Versioning• Views• Full API: Web services, REST, RSS…• Security• Event Receivers• Workflow• Publishing

What to worry about

• UI pattern consistency• Don’t bend it the wrong way

– If you question whether its right, it probably isn’t• Performance considerations• Monitoring

– Resource Usage– No ULS logs, Event Viewer

GETTING STARTED

Approaches

Web UI•Web parts on pages•Site / List Settings

SharePoint Designer•Branding•Business Connectivity Services

Visual Studio 2010 •“ANYTHING”

Don’t work directly on Production

• Develop in Development environments!!!• Great for version 1.0, not so great for 1.1

whilst live users in environment– 24 hour SLA on recovering a site collection

• SharePoint Designer encourages this

Development Environment

• Must have Visual Studio where SharePoint installed for server side development

• Use a “development” site collection in your Office 365 SharePoint 2010 Online environment– Client Object Model

• Install SharePoint 2010 locally on Windows 7

Use a virtual machine

• VMWare Workstation/Sun VirtualBox on Windows 7

• HyperV on dual boot Windows Server 2008 R2/Windows 7

• HyperV on Windows 8 RC• Steal some of IT private cloud to run one ;-)• Azure, CloudShare, fpWeb, Rackspace

TIPS

• Use Sandbox Solutions (default) as can’t use Full-Trust Solutions in SharePoint 2010 Online

• Won’t get compile time warnings on incorrect API usage, only on upload to SharePoint– Use the FxCop rules http

://o365fxcoprules.codeplex.com/

SANDBOXED SOLUTIONS

Sandboxed Solutions

• Restricted API due to multi-tenant environment

• No LOB: Web Services, ATOM, ODBC• No file access• Current site collection scope only• No Page object (JavaScript reg)• Deployed via Site Collection Site Settings

http://msdn.microsoft.com/en-us/library/gg615454.aspx

*smile*

• Office 365 customizations• Faster deploys

– Doesn’t require IISRESET as assemblies not in GAC• No Farm access required

WARNING

• No “Full trust proxies” in Office 365• Only Site Collection Admins can activate if

managed code in packages• Site Collection Admins can deploy these!• Can use Silverlight to overcome some

restrictions

Visual Studio 2012 RC

• Create Silverlight Web Parts• Publish SharePoint Solutions to Remote

SharePoint Servers• Test SharePoint Performance by Using

Profiling Tools• Create Sandboxed Visual Web Parts• Support for JavaScript Debugging and

IntelliSense for JavaScript

http://msdn.microsoft.com/en-us/library/ee290856(VS.110).aspx

Web Part example

• displayed data from a list• perform a SharePoint database query• 20 database queries = 1 resource point• displayed 20 times• site collection would have used 1 resource point of

300 points available• could be displayed 6,000 times in a 24 hour period

the sandbox is turned off until

daily reset

Resource QuotaResource Units Resources

per Point Limit

AbnormalProcessTerminationCount count 1 1

CPUExecutionTime seconds 3,600 60

CriticalExceptionCount Events 10 3

InvocationCount Events <TBD> <TBD>

PercentProcessorTime % 85 100

ProcessCPUCycles cycles 1 x10^11 1 x10^11

ProcessHandleCount items 10,000 1,000

Resource QuotaResource Units Resources

per Point Limit

ProcessIOBytes items 0 1 x10^8

ProcessThreadCount Thread instances 10,000 200

ProcessVirtualBytes Bytes 0 1.0x10^9

SharePointDatabaseQueryCount Query instances 20 100

SharePointDatabaseQueryTime seconds 120 60

UnhandledExceptionCount Unhandled exception instances 50 3

UnresponsiveProcessCount Unresponsive process instances 2

APPLICATION LIFECYCLE MANAGEMENT

Application Lifecycle Management (ALM) is a continuous process of managing the life of an application through governance, development and maintenance.

WikiPedia

ALM is the marriage of business management to software engineering made possible by tools that facilitate and integrate requirements management, architecture, coding, testing, tracking, and release management.

WikiPedia

Three aspects of ALM

David Chappell (2008)

Governance

David Chappell (2008)

Development

David Chappell (2008)

Operations

David Chappell (2008)

Today’s poll question

• I am developing Visual Studio SharePoint projects

• I am packaging all custom code as a WSP• I am using source control• I am using a build server• I am using SPDisposeCheck• I am doing unit testing

SharePoint Designer

• Promotion between environments• Should certain artifacts be packaged as a

WSP?• Manual copying and pasting files• Restricting use by policy• Using third party tools to manage

deployments

One farm, many feature versions active

SPDevWikiV1.0.0.0

SPDevWikiV2.0.0.0

SITE A SITE B SITE C

SPDevWikiV3.0.0.0

SPDevWikiV3.0.0.0

SPDevWikiV1.0.0.0

SPDevWikiV2.0.0.0

SPDevWikiV3.0.0.0

SPDevWikiV3.0.0.0

Build Process

Build Process

Where are you?

No Source Control

Source control

Automated Builds

Automated Testing

Automated Deployment

MIGRATING APPS

Web UI

• Side by side windows– Site Settings– List Settings– Page content

• Windows Explorer– Document Content

SharePoint Designer

• Side by side across windows– Business Connectivity Services– Web Parts– Content Types

• Copy & Paste across windows– Master Pages– Page Layouts– Workflows (no custom activities)

Sandboxed Solutions

• Will work in SharePoint 2010 Online just like Standard or Enterprise

Full-Trust Solutions

• APIs used• Switch to “Sandboxed” and just try it• Run FxCop against it• Change assembly target for Visual Studio 2010

Custom crap!

• Remember, no access to servers AT ALL• So everything must be in Solution Package• No manual deployment of files to file server• We’ve been teaching you this since ‘06

3rd Party Tools

• Graphical User Interface to move Site Collection artifacts and content

• Lots of players– AvePoint– Axceler– MetaVis– MetaLogix

Q&AJeremy Thakewww.NothingButSharePoint.com

jeremy.thake@avepoint.comgplus.to/jthake@jthakewww.linkedin.com/in/jeremythake

References

• Sandboxed Solutions• Office 365 Developer Hub• NothingButSharePoint.com