Download as PDF, PPTX
Uploaded byNCCOMMS
O365Con18 - Working with PowerShell, VS Code and GitHub - Thomas Vochten
This document summarizes Thomas Vochten's presentation on Office 365 & SharePoint Connect 2018. The presentation covers PowerShell past, present and future, essential PowerShell modules and configuration, working with Visual Studio Code, getting started with git, and leveraging the power of the community. Key topics include PowerShell Core being the future, essential PowerShell modules like Plaster and Pester, configuring Visual Studio Code for PowerShell development, and using git for source control and collaboration.
More Related Content
Similar to O365Con18 - Working with PowerShell, VS Code and GitHub - Thomas Vochten
O365Con18 - Working with PowerShell, VS Code and GitHub - Thomas Vochten
- 1. Office 365 &SharePoint Connect 2018 | @thomasvochten IT Pro • Level 200
- 3. Thomas Vochten Microsoft MVP.Solution architect Office 365 & SharePoint. Technical Evangelist. @thomasvochten https://thomasvochten.com mail@thomasvochten.com
- 4. Agenda • PowerShell past,present & future • Essential PowerShell modules & configuration • Working with Visual Studio Code • Getting started with git • Leverage the power of the community
- 5. Why exactly wouldI care?
- 6. Not just fordevelopers Decent Tooling Source Control
- 7. The inconvenient truth… PowerShellis code too!
- 8. Why PowerShell? Many tasksare only available in PowerShell & Avoiding repetition should be a life goal
- 9.
- 10. PowerShell is opensource https://github.com/PowerShell
- 11. PowerShell • The oldand trusted • .NET Framework • Windows only • powershell.exe • versions 1.0 > 5.1 • continues to be supported PowerShell Core • The new kid on the block • .NET Core • Cross-platform • pwsh.exe • version 6 and beyond • the way forward
- 12. PowerShell Core isupon us! •PowerShell Core 6.0 was released in January of 2018 •Currently at version 6.1.1 •Cross-platform: Windows, macOS and Linux sudo apt-get install powershell
- 13.
- 14.
- 15. PowerShell strategy, modules &configuration
- 16. Don’t be anad hoc scripter that only solves problems when they arise
- 17. Have a toolbox! Aimfor a modular approach with • Reusable tools • Predictable outcome • Single responsibility
- 18. Modules 101 Download manuallyor use the PowerShell Gallery https://www.powershellgallery.com Find-Module Install-Module Update-Module Get-Module
- 19. Default Module Locations %userprofile%DocumentsWindowsPowerShellModules C:ProgramFilesWindowsPowerShellModules C:Windowssystem32WindowsPowerShellv1.0Modules
- 20. Essential modules fortool-making Plaster Template-based file and project generator Pester Testing framework
- 21. Demo Working with PowerShellmodules, plaster & pester
- 22. Working with VisualStudio Code
- 23. PowerShell editors Visual StudioCode the new hotness PowerShell ISE deprecated https://code.visualstudio.com
- 24. Why Visual StudioCode? • Intellisense • Debugging • Script Analysis • Built-in git support • Cross-platform • Open source • Highly customizable • Powerful extensions model
- 25. Must Have: PowerShellExtension
- 26. Basic tweaks &customizations • Install extensions • PowerShell • EditorServicesCommandSuite tip • Configure settings such as color scheme • Configure snippets • Add the SharePoint Server “stubs” https://thvo.me/spstubs (Spencer Harbar) • Use a PowerShell profile!
- 27. Demo Visual Studio Code- essential tweaks & customizations, debugging
- 28.
- 29. Git is afree and open source distributed version control system https://git-scm.com (*) Git is not the same as GitHub, you can host git in Azure DevOps or just use it on your machine only…
- 30.
- 31. Git integration withVisual Studio • Separate download & install • Integrated in Visual Studio Code • Supports most basic git commands • Commandline for more advanced scenario’s
- 32. Complementing your toolbox Cmder Opensource console emulator Git & Linux commands integration http://cmder.net Posh-git PowerShell module for git integration in PowerShell Install-module posh-git
- 33. Basic git scenario’s •Just “downloading” code from the internet (cloning) • Creating your own version of the code (forking) • Checking in your changes (commiting) • Updating your copy with changes from the source (fetch & merge)
- 34.
- 35. What to learnnext? 1. Branching 2. Working with remote repositories 3. Creating pull requests 4. Merging your branch
- 36. Leverage the powerof the community!
- 37. Sharing is caring! Everyonecan contribute • Share the things you’re proud of • PowerShell scripts & modules • Samples and tutorials • Documentation • …
- 38. Contributing with git •Fork the repo you want to contribute to • Create a branch for your change • Make & test your changes • Create a pull request • Wait for the pull request to be accepted Learn about pull requests do’s & don’ts…
- 39.