Like a human life, an application’s lifecycle is demarcated by significant events. It begins with an idea: Why don’t we build something that does this? Once the application is created, the next big event is deployment, when the application goes into production. And finally, when it no longer has business value, the application reaches end of life and is removed from service.
Devs“It works on my machine”“Can’t find the source control for this version”“Haven’t got the source control”“I’ve made changes in SharePoint Root”“I copied it to the GAC manually”Admins“We don’t know where to deploy it!”“What version is in Production?”
Automate building of WSPEnforce that all artefacts get deployed via WSP.No manual copying of files to SharePoint RootDisaster RecoveryCheck in policyBuild StampingBuild ServerSeparate serverDon’t install SharePoint on it!Get administrators to push to environments…or automate it (PowerShell 2.0 remoting)
Sandboxed-compatible Visual Web Part This item template enables you to use a visual designer to create SharePoint web parts that can be deployed in a SharePoint 2010 sandboxed solution.Sandboxed Compilation This extension displays build errors when you use types or members in a SharePoint 2010 sandboxed project which are not allowed in the SharePoint sandbox environment.
Acing application lifecycle management in SharePoint
Acing Application Life Cycle Management in SharePoint Jeremy Thake Chief Architect Level: Intermediate
Jeremy ThakeAvePoint LabsAuthor Chief Architect
Agenda• What ALM is• Approaches to ALM• ALM Maturity Model• Getting started• Case Study
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
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
Coding• Source Control – “Copy of” projects – No source code for a build (labeling) – Branching – Shelving
Declarative vs. Imperative• Declaratively – Provision some artifacts – SPI’s built into Visual Studio• Imperatively – Provision / de-provision all – Run class methods – Easier to debug & test – Defensive coding – Code samples – Wrapper classes
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 SITE A SITE B SITE C SPDevWiki SPDevWiki SPDevWiki V18.104.22.168 V22.214.171.124 V126.96.36.199 V188.8.131.52 V184.108.40.206 SPDevWiki SPDevWiki SPDevWiki V220.127.116.11 V18.104.22.168 V22.214.171.124
App Model• Code executed off SharePoint• Can be any language executed on any web server• Client-side object model executed on pages hosted in SharePoint
The Microsoft approach• Visual Studio 2010 Team System – Visual Studio 2010 – Team Foundation Server 2010 – Test Professional 2010 – Project Server 2010• ALL INTEGRATED• TFS in the cloud is coming!
SharePoint 2010 Build server• It doesn’t work out of the box ;-) – Need to put assemblies on TFS server http://msdn.microsoft.com/en-us/ff622991.aspx• SharePoint/TFS Continuous Integration Starter Pack http://sharepointci.codeplex.com/
SharePoint 2013 Build Server• SharePoint Server 2013 Client Components SDK Preview – http://www.microsoft.com/en- us/download/details.aspx?id=30355• Microsoft Windows SDK for Windows 7 and .NET Framework 4 – http://www.microsoft.com/en- us/download/details.aspx?id=8279
The cheaper• Source control – TortoiseHg and Mercurial• Continuous Integration – JetBrains Team City
Approach• BitBucket.org – $10 a month for a mercurial solution• No automated builds – as I do releases...but from Source Code• Using AvePoint’s DocAve Deployment Manager to deploy from Dev to Test to Production