Set up your dev machine in record time with WinGet and Desired State Configuration
summary
Run a single declarative YAML file with WinGet configure and WinGet acts as a local configuration manager calling PowerShell DSC resources (Get/Test/Set) to enable developer mode, add env vars, install Node.js and npm packages, and add Visual Studio workloads. WinGet auto-downloads required PowerShell modules from the PowerShell Gallery, supports dependencies between units, and the Dev Home repo includes samples at aka.ms/dsc.yaml. Feature is experimental in preview, targets stable release around September, and already finds ~300 DSC modules (~1,000 resources).
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:06The problem with environment setup
- 2:17Demo: Automated configuration
- 3:27Leveraging PowerShell DSC
- 5:42How DSC resources work
- 7:18Declarative YAML configurations
- 9:56Winget package management
- 13:07Enabling configuration mode
- 17:34Configuring system state
- 19:31Deconstructing the config file
- 22:40Assertions and components
- 24:19Real-world project setup demo
- 29:16Tips for writing configurations
- 31:12Call to action and feedback
- 33:36Q&A session
related talks
01h 17mDevOps, Desired State, and Microsoft Windows
51mDSC v3: Evolving Declarative Configuration for Modern Systems
45mDesired State Configuration (DSC) Version 3
01h 39mDefine, Develop and Deploy DSC Resources
01h 18mBuilding DSC v3 Resources
44mApplication Provisioning with DSC and Octopus Deploy
44mDesired State Configuration v3
01h 28mYour Superpowered Windows Infrastructure Toolkit: Ansible,...