"Piping" data between packaged scripts
summary
Shows code that actually moves full objects between packaged PowerShell executables using named network pipes and base64-serialized CLI XML, not just text. Uses memory-mapped files or pipes plus gzip compression to shrink a 583k-character payload to about 77k (~86% compression). Demonstrates packaging with SAPIEN/PowerShell Pro Tools, passing encoded object parameters into child exes, and receiving deserialized objects across accounts so an executable running as a service account returns rich structured results.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:25Piping Data between Packaged Partial Scripts
- 3:21Ad Printer Utility
- 4:53What Is Inter-Process Communication
- 8:38Deserialized Object
- 11:38Temporary Files
- 23:20Downsides about Memory Map Files
- 25:47Network Pipes
related talks
39mLinux Shell Debates or: How I Stopped Worrying and Learned to Love PowerShell
43mParallel Execution with PowerShell
47mDeploying software and scripts using ...
03h 04mMastering Making Modules
01h 07mPowerShell: Designed for a Messy World
49mPowerShell in CI/CD Pipelines: A Practical...
46mPowerShell as an MCP Tooling Host: Using MCPServerPS to Supercharge AI-Assisted...
34mWhip Your Scripts into Shape: Optimizing PowerShell for Speed