Managing the SharePoint 2010 Application Lifecycle - Part 1

May 4, 2010Download as PPTX, PDF2 likes830 views

This document discusses managing the lifecycle of SharePoint applications beyond the initial version. It covers using Feature XML and code to upgrade SharePoint applications in a standardized way. The initial build can involve provisioning with XML or code. Feature versioning and the new upgrade framework allow specifying upgrade actions using XML or code. Part 2 will discuss upgrading different artifacts like Features and Assemblies.

Managing the SharePoint Application Lifecycle – beyond version 1.0.0.0PART 1DEV103Chris O’Brien - MVP

Chris O’Brien, MVP, MCSD.Net, MCTSwww.sharepointnutsandbolts.comTwitter: @ChrisO_BrienHands-on developerAuthor of ALM chapter in MVP bookCreator of Content Deployment Wizard toolRegular speaker at UK user group

What is ALM?Definition:Considering all aspects of app through lifetimeKey aspect: managing upgrades and changeSharePoint presents unique challenges – complex platform!

Part 1 (this session)Initial buildFeature development – XML/code

Building Feature XMLUpgrading a SharePoint applicationSP2010 upgradable Features

Using code/XML to upgradePart 2 (Weds 2pm)How to upgrade different artifacts

Versioning recommendationsUpgrading a SharePoint application

Considerations in initial buildDecision: provisioning with XML or code?Drivers to use code approach:Ability to debug provisioning!More control over sequencingUpgrading artifacts requires code anywayBUT, some XML always required:Site definitions, list templates, delegate controls, custom actions

Developing Feature XMLBy handSome ‘startup’ support with VS item templatesCopy/paste from last project NEW – reverse-engineer with toolsStep 1: Save site as template (WSP)Step 2: Import WSP in VS2010

ReceiversNew XMLCan now add event receiver to specific list declaratively:

PropertyBagNew XMLUsed to set list item values declarativelyAlso entries on root web, web, list

WorkflowAssociationNew XMLUsed to add workflow to list/ctype

WebTemplateNew XMLSimilar to site def, for web onlyAlso used in sandbox

CustomActionNew XMLExpanded for ribbon customizationCan also add JS to page (SPSite-scoped)

wsp IMPORTStreamlining the initial site build

WSP import gotchasOOTB site def artifacts includedNOT full fidelity: Can’t do BCS entities, code WFs, list/site defs and more..NOT supported to import 2007 WSP!Round-trip/customized files issueWeb part properties – serialized as binary

WSP import recommendationsDo not use generated VS project itselfSelectively move artifacts into ‘created’ VS project(s)

Approaches for upgradingCreate new featureStaple to existing site def for new sitesScript activation on existing sitesUpgrade existing featureOld way: reactivate featureISSUE: Some artifacts get duplicatedISSUE: May be undesirable for activation code to run multiple timesNew way: upgrade feature

Versioning/upgrading FeaturesVersion attribute now has a purpose!Define what should occur in 1.0.0.0-2.0.0.0UpgradeActions elementXML – some new XML for common scenariosCode – specify method/parameters in CustomUpgradeActions elementNew FeatureUpgrading method – add logic here

Feature upgrade XMLApplyElementManifestsIntegrate new artifacts into existing FeatureSometimes all you need!AddContentTypeFieldAdd columns to content typeMapFileRepoint a file to new location on filesystem (uncustomized files only)

Feature dependenciesCan now depend on specific version of Feature (MinimumVersion)Depended-on Features auto-upgraded where possible Plus same dependency rules as 2007:Cannot depend on lower scopeHidden features cannot have dependencies

UPGRADING A FEATUREUpdating functionality

Triggering upgradeNOT automatic on deployment/ reactivation!Run [Foo].QueryFeatures() to find Features requiring upgradeRun SPFeature.Upgrade() on all/selectedNo UI, PS cmdlet, STSADM cmd to do this

WebSphere Liberty is a Java EE application server built on open source Open Liberty. It uses OSGi services to manage components and provide a dynamic runtime environment. The Liberty kernel launches the OSGi framework which loads configured features as OSGi bundles. Features provide programming models and services for applications. Liberty is lightweight, dynamic, and easy to use making it suitable for cloud applications and microservices.

Running mule as worker role on azureSon Nguyen

Running Mule on Azure can be done using Worker Roles, which are VMs without IIS that perform complex tasks. This document outlines using the Azure toolkit for Eclipse to configure a worker role project that will run Mule standalone and deploy a sample app. Key steps include editing the componentsets.xml file to add Mule, configuring the app deployment, and running the project in the Azure Emulator to test Mule running locally. Improvements mentioned are adding health checks and deploying Mule as a Windows service.

How to Cover All Your Backend Testing Needs with API and UI TestsBlazeMeter

The document discusses API and UI testing and provides guidance on when each type of test should be used. It defines API testing as testing the backend functionality and performance by analyzing hits/second versus response times, while UI testing verifies user scenarios and response times using Selenium. The document recommends using API tests as part of continuous integration builds, before adding new services, and for staging performance tests, while recommending UI tests before major releases and events. It also provides an overview of how testing can integrate into the application lifecycle from unit testing to production load testing.

Introducing Mule Application and APIJitendra Bafna

Mule applications can consist of single or multiple connected flows that accept messages from external sources through message sources. Messages are then processed through message processors in a flow. Mule applications are written in XML and deployed visually to a Mule runtime, which can be on-premise or cloud-based. The Mule runtime handles requests from different applications concurrently and enforces API governance policies. Anypoint Studio is an Eclipse-based IDE that provides pre-built connectors and tools for developing, testing, and deploying Mule applications to Mule runtime editions. Mule APIs can be designed using RAML and support HTTP methods, then published through Anypoint Portal for public or private use.

Serverless meetup - OpenWhisk overview and architectureSandeep Paliwal

OpenWhisk is an open source serverless cloud platform that runs user-provided code in response to events or direct invocations. It was started by IBM and supports multiple programming languages and invocation models. The OpenWhisk architecture uses Nginx as an API gateway, a Scala controller to handle requests, Consul for service discovery, Kafka for messaging, Docker containers to run code, and CouchDB for persistent storage. This allows user code to be quickly deployed and executed in response to events in a scalable and reliable manner.

Laravel and CodeIgniter: pros & consElenorWisozk

automationframeworkVijay Rangaiah

The Marlabs Automation Framework uses 3 projects and integrates with the open source Test Link test management tool. The framework includes a Java Swings UI controller application for handling test script execution and taking input from exported Test Link XML files. An automation test suite is built using core Java for executing test scripts and generating reports. A J2EE web project generates online results reports using Apache Tomcat. The framework generates results in Excel, XML, HTML formats as well as online web reports. Skills required include core Java, web programming, databases, Test Link, and Selenium.

ATLAS Automation POCaakashmc

The document discusses automating testing of the Alchemy software product using the ATLAS test automation framework. Some key points: 1. ATLAS was used to automate over 7,000 test cases for Alchemy, automating 900 of them. This reduced regression testing time by up to 30% and improved quality. 2. ATLAS features a keyword-driven and data-driven testing approach using a tabular syntax. It generates HTML reports and integrates with build systems. 3. An example annotation module automation for Alchemy is demonstrated, along with sample test case, log, and report outputs from ATLAS.

Metrics & Challenges for Testing Streaming Applications in 2019Sarah Elson

Streaming rich media has become an integral part of our daily lives. From watching tutorials on YouTube, Udemy etc. to playing RPGs(Role-Playing Games) on the internet, a major percentage of internet traffic nowadays spends their data on browsing through audio and video contents. With the data speed increasing day by day, media streaming has become the primary way of spreading information to the crowd.

Deploy mule applicationSon Nguyen

The document discusses deploying Mule applications using the Mule Management Console (MMC). The MMC provides centralized management and monitoring of Mule deployments. It allows users to deploy, undeploy, and redeploy applications to Mule servers. The Deployments tab in MMC lists all provisioned applications and their statuses, and allows users to perform actions like deploying, undeploying, and redeploying applications. Users can also create new deployment groups to specify servers and applications.

Modern App Development with the SharePoint FrameworkPete Filicetti

This document discusses building SharePoint Framework (SPFx) client-side web parts using modern tools and frameworks. It covers using tools like Yeoman and Gulp to scaffold, build, and deploy SPFx solutions built with React and Fabric components. The session objectives are to discuss SPFx issues and contributions on GitHub and Dev.office.com, and to learn how to package and deploy SPFx solutions to SharePoint. The document promotes networking with other SharePoint professionals after the session at a local bar.

ASP.NET Core 1.0 OverviewShahed Chowdhuri

Automationfreeuser_321

The Selenium framework is built using Ruby and Selenium/Webdriver tools. It can execute scripts using Ant commands and allows prioritizing scripts by tag names. The framework integrates with Hudson by configuring and executing test runs via Hudson jobs. Hudson jobs can be configured to trigger builds and collect artifacts and test results. Hudson then executes the builds and allows analyzing results. iAnalyze aims to optimize testing time through a snapshot of build health and storing prior execution data to help analyze scripts. It offers customized reports and graphs along with centralized data sharing between QA teams.

What's new in ALM using Visual Studio 2013 and Team Foundation ServiceMicrosoft Visual Studio

The document discusses application lifecycle trends, including frequent updates for on-premises products and 3-week sprints for Visual Studio Online. It also describes a continuous deployment solution for .NET teams that automates deployments from development to production using Release Management Client and Server with full traceability. The solution supports configuration-based deployments across environments.

KKBOX WWDC17 Security - AntonyLiyao Chen

This document summarizes the WWDC 2017 reading session. It discusses topics around network security standards, privacy and apps, advances in networking technology, and new features for Apple Pay Wallet. Specific areas covered include app transport security, privacy prompts, location services, device check, multipath TCP, URL session updates, and enhanced support for donations and error handling in Apple Pay.

Bring Order to the Chaos: Take the MVC PlungeColdFusionConference

The document summarizes a presentation given at ColdFusion Summit 2016 about migrating ColdFusion applications from a procedural style to using the Model-View-Controller (MVC) pattern. It begins with an introduction to the speaker and agenda. It then discusses the downsides of procedural code, introduces MVC, and provides examples of MVC code using the Framework-One ColdFusion MVC framework. The presentation reviews the pros and cons of MVC and discusses strategies for migrating legacy applications.

Akash 2013CA05 software testing presentation -seleniumAkash Verma

Selenium IDE is a tool that allows users to record, play back, and debug tests of web applications directly inside their web browser. It was originally developed by Shinya Kastani as an extension of the Selenium core JavaScript code. Selenium IDE records user interactions on a website as functions and allows those functions to be played back to test the site's functionality. While only compatible with web-based applications, Selenium IDE provides advantages like supporting multiple browsers and platforms, error handling, and test data-driven testing. It works by sending test commands from a client library to the Selenium server, which then executes those commands using the Mozilla Firefox browser and returns testing results to the user.

Accelerating time to delivery modern tools for cobol developmentMicro Focus

This document discusses tools that can accelerate COBOL development time, including project templates, code snippets, cross-platform development with Eclipse, integrating COBOL with other technologies like .NET and Java, and using standard build and deployment tools like MSBuild and Ant. It demonstrates project templates, code snippets, cross-platform development, and how to integrate 3rd party tools.

Composer talk by Maxim Romanovskyphp-user-group-minsk

IAM EclipseCon 2009mpoindexter

The document discusses Eclipse IAM, which provides Maven integration for Eclipse. It allows users to import existing Maven projects, create projects from archetypes, edit POMs, search artifact repositories, manage dependencies, run Maven goals from Eclipse, and more. The goals are to simplify using Maven in Eclipse, integrate without reinventing existing components, and support other integrations. It has been in development since 2007 and is actively maintained by several committers.

Building your first android app using xamarin (Gill Cleeren)Visug

Do you have a great knowledge about C#? Maybe you’ve already built a great mobile app on Windows Phone or Windows 8 or even Windows 10? Would you like to be able to use your knowledge to build an Android app without having to resort to other languages or IDEs? This is possible using Xamarin! In this session, Gill Cleeren will take you through the creation of your first Android application: Joe’s Coffee Store. Along the way, you will learn the basic concepts of Android such as Activities and see how we can use these from Xamarin.Android. We’ll need to connect with services to get access to data and we’ll learn how to navigate in the app. You’ll see we can do this all of this directly from Visual Studio. We will finish the session by looking at how we can deploy the application to the Google Play Store so it’s ready for our users! You’ll walk away wanting to port your code to Android!

Mockingbird – mock apiSagar Rao

SPCSEA 2013 - Upgrading to SharePoint 2013Michael Noel

This document provides an overview of best practices for upgrading to SharePoint 2013. It discusses upgrade fundamentals including requirements, supported version upgrades, and the Microsoft versus third-party approaches. It covers pre-upgrade tasks like claims migration and content database testing. Detailed steps are provided for upgrading service applications like the managed metadata service and user profile sync. Post-upgrade health checks and visual changes are also addressed. The presentation emphasizes testing upgrades, addressing issues proactively, and proceeding cautiously.

SharePoint 2013 MigrationVishal Gupta

This document discusses approaches for migrating content from earlier versions of SharePoint like MOSS 2007 and SharePoint 2010 to SharePoint 2013. It covers key drivers for upgrading like improved search and productivity. Common migration approaches like database attach and in-place are described. The ideal approach is a two-phase migration, first to SharePoint 2010 and then to 2013. The migration cycle of plan, prepare, test, implement and validate is outlined. Important steps for each phase like backing up databases and testing are highlighted. Potential problems in migration and tools to help like Metalogix Content Manager are also summarized.

SharePoint Taxonomy and Metadata 11-19-09Stephanie Lemieux

Best Practices for Organizing Documents in SharePoint 2010Agnes Molnar

This document discusses best practices for organizing documents in SharePoint 2010. It recommends using document sets instead of folders when hierarchy is not needed or when additional capabilities are required. It also recommends centrally managing metadata and content types at the top site collection level. Finally, it suggests using content organizer rules to automatically route documents to the proper location based on properties, improving organization and searchability.

More Related Content

What's hot (18)

Serverless meetup - OpenWhisk overview and architectureSandeep Paliwal

Laravel and CodeIgniter: pros & consElenorWisozk

automationframeworkVijay Rangaiah

ATLAS Automation POCaakashmc

Metrics & Challenges for Testing Streaming Applications in 2019Sarah Elson

Deploy mule applicationSon Nguyen

Modern App Development with the SharePoint FrameworkPete Filicetti

ASP.NET Core 1.0 OverviewShahed Chowdhuri

Automationfreeuser_321

What's new in ALM using Visual Studio 2013 and Team Foundation ServiceMicrosoft Visual Studio

KKBOX WWDC17 Security - AntonyLiyao Chen

Bring Order to the Chaos: Take the MVC PlungeColdFusionConference

Akash 2013CA05 software testing presentation -seleniumAkash Verma

Accelerating time to delivery modern tools for cobol developmentMicro Focus

Composer talk by Maxim Romanovskyphp-user-group-minsk

IAM EclipseCon 2009mpoindexter

Building your first android app using xamarin (Gill Cleeren)Visug

Mockingbird – mock apiSagar Rao

Serverless meetup - OpenWhisk overview and architectureSandeep Paliwal

Laravel and CodeIgniter: pros & consElenorWisozk

automationframeworkVijay Rangaiah

ATLAS Automation POCaakashmc

Metrics & Challenges for Testing Streaming Applications in 2019Sarah Elson

Deploy mule applicationSon Nguyen

Modern App Development with the SharePoint FrameworkPete Filicetti

ASP.NET Core 1.0 OverviewShahed Chowdhuri

Automationfreeuser_321

What's new in ALM using Visual Studio 2013 and Team Foundation ServiceMicrosoft Visual Studio

KKBOX WWDC17 Security - AntonyLiyao Chen

Bring Order to the Chaos: Take the MVC PlungeColdFusionConference

Akash 2013CA05 software testing presentation -seleniumAkash Verma

Accelerating time to delivery modern tools for cobol developmentMicro Focus

Composer talk by Maxim Romanovskyphp-user-group-minsk

IAM EclipseCon 2009mpoindexter

Building your first android app using xamarin (Gill Cleeren)Visug

Mockingbird – mock apiSagar Rao

Viewers also liked (6)

SPCSEA 2013 - Upgrading to SharePoint 2013Michael Noel

SharePoint 2013 MigrationVishal Gupta

SharePoint Taxonomy and Metadata 11-19-09Stephanie Lemieux

Best Practices for Organizing Documents in SharePoint 2010Agnes Molnar

Access Services in SharePoint 2010 - All You Need to KnowNik Patel

This document provides an overview of Access Services in SharePoint 2010. It discusses the benefits of Access Services, how to configure it on a SharePoint farm, and how to deploy Access databases to Access Services. It also covers limitations, performance tuning, and considerations for migrating Access databases. The presentation aims to help administrators and analysts understand Access Services and identify best practices.

10 Reasons your SharePoint Migration FailedBenjamin Niaulin

This document provides 10 reasons why a SharePoint migration may fail: 1) Lack of knowledge about SharePoint and its underlying technologies. 2) Ignoring training which helps with adoption and success. 3) Poor communication about the changes to users. 4) Relying only on database attach upgrades without considering custom solutions. 5) Not building a new architecture to take advantage of SharePoint 2013 features. 6) Not inventorying and testing all sites for upgrade issues. 7) Lack of governance, information architecture, and migration planning. 8) Not defining clear and measurable goals for a successful migration. 9) Underestimating the importance of branding for user experience

SPCSEA 2013 - Upgrading to SharePoint 2013Michael Noel

SharePoint 2013 MigrationVishal Gupta

SharePoint Taxonomy and Metadata 11-19-09Stephanie Lemieux

Best Practices for Organizing Documents in SharePoint 2010Agnes Molnar

Access Services in SharePoint 2010 - All You Need to KnowNik Patel

10 Reasons your SharePoint Migration FailedBenjamin Niaulin

Similar to Managing the SharePoint 2010 Application Lifecycle - Part 1 (20)

Managing the SharePoint 2010 Application Lifecycle - Part 2Chris O'Brien

This document discusses strategies for upgrading SharePoint applications beyond the initial version. It covers upgrading different artifacts like content types, files, and lists using techniques like applying element manifests or mapping files to new locations. The document also addresses upgrading features through the new version attribute and upgrade actions element. It provides recommendations for versioning assemblies and features to track changes across farm upgrades. Special considerations for upgrading workflows are also outlined.

Developer application lifecycle process and tools - v.5Ivan Sanders

SharePoint Connections Coast to Coast Migrating SharePoint 2007 Solutions to ...Ivan Sanders

In the wake of the SharePoint 2010 release, many companies are now looking to migrate their web sites from SharePoint 2007 to 2010. However, where do you start? What are the new features that enable you to migrate your site? How do you work with your developers and administrators to help them get started? If these are the questions you’re trying to answer, then you’ll not want to miss this session. You’ll learn about the features, tools and processes that will help you move your 2007 assets to 2010.

Practical Guidance for SharePoint 2010 UpgradeJoel Oleson

Chris O'Brien - Introduction to the SharePoint Framework for developersChris O'Brien

Building and Deployment of Drupal sites with Features and ContextSvilen Sabev

The document summarizes a presentation about building and deploying Drupal sites using the Features and Context modules. It discusses how Features allows developers to package configurations like content types, views, and permissions into reusable modules. Context allows managing different site sections or "contexts" through conditions and reactions. The presentation provides examples of using both modules and recommends best practices for organizing configurations in Features.

Features and Context Overviewbrentratliff

Борис Трофимов. Continuous Database migration-это просто!Volha Banadyseva

This document discusses techniques for continuous database migration. It introduces Carbon5, an open source database migration framework. Carbon5 works by having each schema change stored as a separate SQL script file. It tracks which changes have been applied to prevent duplicate executions. The document contrasts Maven-driven and embedded modes of using Carbon5. With Maven-driven, migrations run as Maven goals; with embedded, a bean handles migrations on application startup. Best practices discussed include feature-based script organization and avoiding direct database changes outside the framework. Alternatives like Flyway and NoSQL migration approaches are also briefly covered.

Continuous DB migration based on carbon5 frameworkb0ris_1

This document discusses techniques for continuous database migration. It introduces Carbon5, an open source database migration framework. Carbon5 works by having each schema change stored as a separate SQL script file. When run, it checks which changes have not been applied and executes them. Carbon5 can be used in maven-driven or embedded modes. Maven-driven mode integrates with maven builds, while embedded mode performs checks on application startup. Best practices include feature-driven development of SQL files and keeping database configuration centralized. The document also discusses approaches for NoSQL databases, which may handle migrations differently.

Cetas - Application Development ServicesKabilan D

SharePoint 2010 DevelopmentElaine Van Bergen

[Portland 365Sat] PCF Custom Controls⚡ Danish Naglekar

This document provides an overview of PowerApps custom controls (PCF). PCF allows developers to create reusable custom controls with enhanced capabilities compared to web resources. It discusses the PCF project structure, including the manifest and index files. PCF controls can be built with TypeScript, React, and other frameworks. The document demonstrates how to set up a development environment and build a PCF control. It also provides resources for the PCF community and links for additional documentation.

Netbeans 6.1 TalkAngad Singh

Strategies and Tips for Building Enterprise Drupal Applications - PNWDS 2013Mack Hardy

Mack Hardy, Dave Tarc, Damien Norris of Affinity Bridge presenting at Pacific Northwest Drupal Summit in Vancouver, October 5th, 2013. The presentation walks through management of releases, deployment strategies and build strategies with drupal features, git, and make files. Performance and caching is also covered, as well as specific tips and tricks for configuring apache and managing private files.

Best Practices Configuring And Developing Share Point SolutionsAlexander Meijers

SPUnite17 Building Great Client Side Web Parts with SPFxNCCOMMS

This document provides an overview and agenda for a presentation on building great client-side web parts for SharePoint with the SharePoint Framework (SPFx), PnP-JS-Core, ReactJS, and Office UI Fabric. The presentation covers why to use SPFx instead of traditional JavaScript injection, introduces key concepts and technologies like ReactJS and Office UI Fabric, demonstrates how to call the SharePoint REST API with PnP-JS-Core, and discusses building web parts by bringing these technologies together. It also outlines the SPFx roadmap and conclusions that modern tools are now available for building reusable SharePoint components.

COB - Azure Functions for Office 365 developersChris O'Brien

Mobile and IBM Worklight Best PracticesAndrew Ferrier

This document provides an overview and best practices for developing mobile applications using IBM Worklight. It discusses development tools and frameworks, RESTful services, Worklight adapters, and the Worklight application lifecycle including building, testing, and deploying applications. It also covers updating applications and provides other tips such as preferring a single page architecture and versioning services and adapters. The document is intended for a WebSphere User Group presentation on Worklight mobile development.

SPUnite17 Become a Developer Hero by Building Office Add insNCCOMMS

1) Office add-ins allow developers to build extensions that integrate with Office applications and can be distributed through the Office Store or deployed within an organization. 2) Developers can use popular web technologies like HTML, CSS, and JavaScript to build add-ins that provide a native experience across Office platforms. 3) The Office UI Fabric framework provides styling and components to help add-ins look and feel consistent with Office applications.

Feature Based Web Development with Bazaaryogomozilla

Managing the SharePoint 2010 Application Lifecycle - Part 2Chris O'Brien

Developer application lifecycle process and tools - v.5Ivan Sanders

SharePoint Connections Coast to Coast Migrating SharePoint 2007 Solutions to ...Ivan Sanders

Practical Guidance for SharePoint 2010 UpgradeJoel Oleson

Chris O'Brien - Introduction to the SharePoint Framework for developersChris O'Brien

Building and Deployment of Drupal sites with Features and ContextSvilen Sabev

Features and Context Overviewbrentratliff

Борис Трофимов. Continuous Database migration-это просто!Volha Banadyseva

Continuous DB migration based on carbon5 frameworkb0ris_1

Cetas - Application Development ServicesKabilan D

SharePoint 2010 DevelopmentElaine Van Bergen

[Portland 365Sat] PCF Custom Controls⚡ Danish Naglekar

Netbeans 6.1 TalkAngad Singh

Strategies and Tips for Building Enterprise Drupal Applications - PNWDS 2013Mack Hardy

Best Practices Configuring And Developing Share Point SolutionsAlexander Meijers

SPUnite17 Building Great Client Side Web Parts with SPFxNCCOMMS

COB - Azure Functions for Office 365 developersChris O'Brien

Mobile and IBM Worklight Best PracticesAndrew Ferrier

SPUnite17 Become a Developer Hero by Building Office Add insNCCOMMS

Feature Based Web Development with Bazaaryogomozilla

More from Chris O'Brien (20)

Chris O'Brien - Building AI into Power Platform solutionsChris O'Brien

Chris OBrien - Azure DevOps for managing workChris O'Brien

Chris O'Brien - Ignite 2019 announcements and selected roadmapsChris O'Brien

COB ESPC18 - Rich PowerApps with offline supportChris O'Brien

COB - PowerApps - the good, the bad and the ugly - early 2018Chris O'Brien

Chris OBrien - Pitfalls when developing with the SharePoint Framework (SPFx)Chris O'Brien

Chris O'Brien - Best bits of Azure for Office 365/SharePoint developersChris O'Brien

Chris O'Brien - Intro to Power BI for Office 365 devs (March 2017)Chris O'Brien

Chris O'Brien - Modern SharePoint sites and the SharePoint Framework - referenceChris O'Brien

Application Lifecycle Management for Office 365 developmentChris O'Brien

For teams doing cloud-friendly SharePoint or Office 365 development, apps will be a key area of focus - be they SharePoint add-ins or the newer Office 365/Azure AD apps. ASP.NET (typically MVC) is a common platform here, and fortunately ALM and Continuous Integration become MUCH easier - finally, an end to "it’s harder because it's SharePoint!" We'll demonstrate how Visual Studio Online and Azure Web Apps are a winning combination for “continuous deployment”, and also how features such as "Deployment Slots" in Azure can help with dev and test environments, and also the upgrade/push-to-live process. Several demos will ensure you’re covered for developing both SharePoint add-ins and Office 365 apps.

Do's and don'ts for Office 365 developmentChris O'Brien

A session I gave at the European SharePoint Conference 2015. Abstract: The "rules" of SharePoint development have changed - although MSDN documentation often lags behind, the Office 365 Product Group tell us we're no longer supposed to use custom master pages, WebTemplates or deploy our fields and content types in XML. This means core concepts and guidelines that have been around for 7 or 8 years no longer hold true! Clearly this is a massive change - but do we always need to adhere to these new rules? Or are there times when it's OK to use less-preferred (but still supported) approaches? In this session we look at the reasons behind Microsoft's change of position, and the associated thinking you need to do in the real world. In this session you will learn: 1. A discussion of the key changes in developer guidance 2. A technical deep-dive (with demos) into the new approaches Microsoft recommend 3. Consideration of the circumstances where you might choose NOT to adhere to the guidance, and why

Chris O'Brien - Comparing SharePoint add-ins (apps) with Office 365 appsChris O'Brien

A presentation I gave at SharePoint Evolutions 2015. Here, I compare SharePoint apps (now renamed "SharePoint Add-Ins" as of April 2015!) and the newer flavour of app development, Office 365 apps. It focuses primarily on the perspective of a development team implementing the app - and factors to consider when deciding between the two approaches. However, to do this we must consider end-user and administration aspects, as well as code/development. Key agenda points: - Changes in SharePoint development - Apps, 2 years on.. - SharePoint Add-Ins – a recap - Office 365 apps - Why did Microsoft introduce these? What do they promise? - Comparing SharePoint Add-Ins with Office 365 apps - For the end-user, administrator and developer - Summary

Chris OBrien - Weaving Enterprise Solutions into Office ProductsChris O'Brien

Chris O'Brien - Modern SharePoint development: techniques for moving code off...Chris O'Brien

This document discusses modern techniques for developing for SharePoint in a cloud-friendly way by moving code off SharePoint servers. It covers remote event receivers, PowerShell with CSOM, and Microsoft's App Model Samples. Remote event receivers allow executing code in response to events. PowerShell and CSOM is a powerful combination. The App Model Samples provide helper libraries and examples for common tasks like uploading files, provisioning sites and managing terms. While Microsoft's optimal approach is debated, these techniques allow customizations to be deployed to Office 365.

Chris O'Brien - Customizing the SharePoint/Office 365 UI with JavaScript (ESP...Chris O'Brien

Deep dive into SharePoint 2013 hosted apps - Chris OBrienChris O'Brien

Customizing the SharePoint 2013 user interface with JavaScript - Chris OBrienChris O'Brien

SP2013 for Developers - Chris O'BrienChris O'Brien

The document provides guidance on developing apps for SharePoint instead of classic solutions whenever possible. It discusses SharePoint-hosted and cloud apps. It also discusses whether all apps from the SharePoint Store will be allowed to be installed and if customizations will be developed as apps. Finally, it provides information on web parts, search results, and control templates used to render items for web parts.

Getting to grips with SharePoint 2013 apps - Chris O'BrienChris O'Brien

SharePoint Ribbon Deep DiveChris O'Brien