A Scripters Next Step...
summary
Half-day workshop moves PowerShell scripters into C# by having participants build a .NET Minimal API from scratch, wire it to a Postgres database (Neon) with Npgsql and Dapper, implement a repository pattern and CRUD endpoints, and add an API key middleware for simple authorization. Demo shows class/constructor patterns, global usings, embedding PowerShell runspaces, and a successful GET and authenticated PUT that updates the cloud DB, while live-demo hiccups around builds and runtime publishing surface practical pitfalls.
AI-written summary · about
chapters (20)
- 0:00Scriptor's next step intro
- 0:22PowerShell to C# transition
- 1:07Speaker background
- 2:29Software in modern ops
- 3:11AI replacing roles fears
- 4:15C# better than Python for PowerShell
- 8:50APIs glue of the internet
- 11:14C# and .NET project structure
- 14:06First C# console app demo
- 23:36PowerShell vs C# control flow
- 32:34C# classes and objects demo
- 41:24Break time
- 1:00:38REST API with ASP.NET Core
- 1:31:00API database connectivity
- 2:00:25API CRUD operations
- 2:30:05API authentication
- 3:04:30Q&A on API design
- 3:14:12PowerShell in .NET apps
- 3:26:45Self-contained executables
- 3:40:09Closing remarks
related talks
01h 33mA hands-on lab working
01h 26mGetting Ahead By Deleting Code
47mThink Abstract, abstracting your PowerShell code
01h 45mWriting Award Winning PowerShell Functions and Script Modules
52mA vendors perspective
43mPowerShell Tooling
40mFrom Chaos to Clarity: Taming Data with PowerShell
46mFrom Script to Tool: Building Robust, Meaningful Tools with PowerShell