SPSVB Sponsors Platinum Gold Silver

SharePint ATC Immediately following SPSVB Closing Some appetizers will be provided

Understanding where to start on SharePoint Development M. Paul Telkamp Cutulus

Who am I? SharePoint know it all (mostly) Reluctenly got into web coding by being the only person willing to do it Started with SharePoint in 2004 with SharePoint Portal Server 2003 I was handed the Administrator’s Companion to learn it Power User / Administration Became an InfoPath wizard that led to next position Moved to SharePoint 2007 as an Admin became a Developer Learned through a lot of hard knocks but kept learning how to do it better Worked in multiple environments (Single server to 16 server farm and everthing in between) Worked in multiple industries Food Service, Cable, Real Estate, Financial, Military, Retail, Manufacturing and many more

Why I prepared this Help anyone considering potential SharePoint solutions to make informed decisions I have seen good environments get trashed by bad solutions that were intended to fix problems I hate hacked together solutions to get something working As an admin, I want to minimize the time I have to perform those functions IE – I hate looking at ULS logs for issues As a developer, I don’t want to build a solution and create issues I want to separate my work from the environment https://sharepoint.stackexchange.com/questions/206685/sharepoint-development-past-and-future-how-to-keep-calm

Where have we been OSE Farm solution model Sandbox solutions App Model Office Server Extentions Business Productivity Online Standard Suite Farm solution model Sandbox solutions App Model SPFX Aug 15, 2016

Where have we been 2003 - 2007 Farm solution model few knew how until 2007 unless you were a VAR Limited ways to make SharePoint functional 2010 Sandbox solutions Client-side object-model APIs for JavaScript, Silverlight, and .NET applications 2013 App Model UI: JSLink, MDS, theme packs. No WYSIWYG in SP Designer 2016 and expected future versions SPFx 2019 Modern sites, pages, lists, and libraries

SharePoint Object Model x4 of these

Sandboxed Object Model

How do I do that? https://sharepoint.stackexchange.com/questions/219459/sp-2016-branding-on-premises

Dev Options O365: On Prem: Pros: Cons: Notes: Server Solution Sandbox Solutions Script Editor WP Add-in (MS SPApp store) SPFx Page Viewer O365: NA Available On Prem: Available (deprecated feature) Pros: Full farm control Allows in site use Local to the page (Single Page Apps) Can use REST / CSOM / JSOM to interact with SharePoint Can use REST / CSOM / JSOM to interact with SharePoint but is running in context of SharePoint Runs on any page Cons: Full farm control (security risks) Complicated and limited in use Local to the page and complicated with NoScript pages (My Sites, Team Sites, Group Sites) External to SharePoint and viewed via iFrames New way of developing in SharePoint (learning curve) Limited or no functionality within SharePoint Notes: Visual Studio Varies Visual Studio or VS Code MS has started moving to using this as the model for new or upgraded features

Why does the way I develop matter? Because hopefully you will be migrating your code at some point Migration of your solution needs to be as unintrusive as possible so that when the migration plan is chosen, you can minimize the timeline to implement Every customization will need to be evaluated in the next environment and version Any disruption to service can impact a business’s ability to make money or be productive Who wants to have the Admin to the VP or President calling saying they can’t do their work? Don’t develop in PROD – You don’t want a black eye

Tools available The tools you have access to and environment variables will dictate what you can use Security concerns will also dictate what you can do There are ways around this if you have to

Tools available*

What is my solution? Tagline Build apps in hours—not months—that easily connect to data, use Excel-like expressions to add logic, and run on the web, iOS, and Android devices Make sense of your data through interactive, real-time dashboards and unlock the insights needed to drive your business forward. Include powerful workflow automation directly in your apps with a no-code approach that connects to hundreds of popular apps and services. HTML editor freeware for creating or modifying Microsoft SharePoint sites, workflows and web pages For designing, distributing, filling and submitting electronic forms containing structured data. IDE for a creative launching pad that you can use to edit, debug, and build code, and then publish an app. a source code editor developed by Microsoft for Windows, Linux and macOS. It includes support for debugging, embedded Git control, syntax highlighting, intelligent code completion, snippets, and code refactoring. Farm solution, Web App, or Tenent Yes Yes (App Store deployment) Features App Model Site Collection (SPSite) Site (SPWeb) Single page App Yes, but still not in SharePoint proper Yes, but limited functionality and depricated Web part Custom Templates (Sites / Lists / Libraries / Content Types / Columns) Workflows Branding Yes, but very complex to implement https://docs.microsoft.com/en-us/sharepoint/dev/schema/sharepoint-add-in-schemas

Signup for O365 Dev Program & Github https://developer.microsoft.com/en-us/office/dev-program https://github.com/join

Nodejs and NPM Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine This is basically your web server / app engine when running it, but that is an over simplification CLI for running commands NPM is the package manager for JavaScript and the world’s largest software registry Used to install and register your JS files

Yeoman & Gulp Yeoman helps you to kickstart new projects, prescribing best practices and tools to help you stay productive The power of this is just staggering Gulps is a toolkit for automating painful or time- consuming tasks in your development workflow, so you can stop messing around and build something Time saving and extendable.

Visual Studio & VS Code VS is a full blown IDE Don’t switch just because of the suggestion to use VSC VS Code is a source code editor Think VS Lite

React / Angular / TypeScript / Vue TypeScript is an open-source programming language developed and maintained by Microsoft. It is a strict syntactical superset of JavaScript, and adds optional static typing to the language. TypeScript is designed for development of large applications and transcompiles to JavaScript React is a JavaScript library for building user interfaces. It is maintained by Facebook and a community of individual developers and companies. React can be used as a base in the development of single-page or mobile applications AngularJS is a JavaScript-based open-source front-end web application framework mainly maintained by Google and by a community of individuals and corporations to address many of the challenges encountered in developing single-page applications. Vue.js is an open-source JavaScript framework for building user interfaces and single-page applications

You can use any JS library As long as you import it from NPM or add it to your project you can use almost any JS library

Pick your tools Use what works best

Questions? Oh and use Node for building out some other nifty applications Contact me: Cutulus@gmail.com

SharePint ATC Immediately following SPSVB Closing Some appetizers will be provided

SPSVB Sponsors Platinum Gold Silver

Links https://docs.microsoft.com/en-us/sharepoint/dev/ https://github.com/Cutulus https://nodejs.org/download/release/v8.9.4/ (SPFx needs a lower version than most other Node and NPM files) https://docs.microsoft.com/en-us/sharepoint/dev/sp-add- ins/sharepoint-net-server-csom-jsom-and-rest-api-index