I'm working on a self-contained tool to download and install multiple versions of PowerShell side-by-side, it also supports virtual environments for modules. Would it help to achieve what you're doing? github.com/devolutions/...
Do you install PowerShell and PowerShell modules in environments with restricted Internet access? If so, what's your current way of doing it? What would be your dream solution?
If you wrap git, please test with multiple accounts, and ensure you are never calling the git cli in an ambiguous way, without the git repository URL. Getting repeated account selection prompts from the git credential manager is a big no-no: github.com/microsoft/ap...
Who's getting stoked for @powershellsummit.org ? Look at that beautiful schedule. pshsummit2026.sched.com
1007 days since we released Avalonia 11.
Avalonia 12.0 is available NuGet now!
Our mantra has been: PERFORMANCE, PERFORMANCE, PERFORMANCE!
avaloniaui.net/blog/avalon...
Same thing for any task that requires Windows - how can I trust any "blind" changes made in a Linux runner when the only way to validate changes is to actually run the code on Windows? For instance, changes that deal with WinGet integration, etc. I wish I could select runners
When using my laptop, I can have GitHub Copilot in VSCode create workflows which are repeatedly pushed to a branch and executed, after which the artifacts for Windows, macOS and Linux are checked. I can't do this within GitHub Copilot coding agent easily. It'll just guess
GitHub Copilot coding agent no longer creates pull requests by default. This means I can fire a lot of tasks from my phone, without opening PRs which I could not review first. Now the biggest issue is getting changes validated on the right runners, since it always runs on Linux
I decided to rename my module. Now it's called "GliderUI":
github.com/mdgrs-mei/Gl...
Cross-platform desktop GUI framework for #PowerShell built using Avalonia.
- Runs on Windows, macOS and Linux
- You can build GUIs by code or XAML
- No more freezing GUIs
Thanks, I knew there was a post-mortem blog post coming out soon, but I hadn't seen it yet
There's the pwsh-7 alias already which would fit the bill
I still have to figure out a nice way to get "pwsh" pointing to a multi-pwsh controlled installation, before the "regular" one in PATH 😜
dotnet tools are only practical if you already have the dotnet CLI, they're not a shortcut outside of .NET tooling, really.
Anyway, I think you'll like this better 😜 github.com/Devolutions/...
Sorry for the confusion. I don't really care for using the .NET tool directly, but since it's a nuget package on nuget.org, it's much easier for me to write custom msbuild code to fetch and extract pwsh.dll and pwsh.runtimeconfig.json which are missing from the matching Microsoft.PowerShell.SDK
I'm basically solving my own wish, which will allow me to have a usable pwsh executable bundled with RDM *without having to ship a full copy of PowerShell a second time, as it will reuse the PowerShell SDK*: bsky.app/profile/awak...
You can already install multi-pwsh, but what I'm working on right now is automatically import pwsh.dll, pwsh.runtimeconfig.json in a .NET app using the PowerShell SDK, such that I can just put in pwsh.exe (renamed multi-pwsh) as the apphost executable
I was going to go for a vanilla pwsh apphost executable, but I guess I just found a good reason to use multi-pwsh as my apphost executable for PowerShell imported from the PowerShell SDK 😜
Hum... it looks like the nuget package expects a dotnet shim executable to be used through "dotnet tool", but it's true that the apphost executable included inside the nupkg is for a single platform. Good catch, I was going to reuse the single-arch apphost executable
RPC for LLMs. tools along with instructions on how to call them, in natural language
TIL: there's a nuget package for PowerShell that you can install as a dotnet tool: www.nuget.org/packages/Pow...
It's going to be fun to see how Anthropic's lawyers are going to try taking it down anyway
I wish there was an easy way for a .NET application to import the PowerShell SDK *with the pwsh executable*. A full copy of PowerShell is already included, except the main executable entry point, which I have a use case for
Back at the cottage ❄️🐕
Tell me what you think! I'd like to keep improving it
Yes, I'm creating them under ~/.pwsh/venv by default when specifying just the name, but I have added support for environment variables to override the paths, and also accept a full path to the venv. I'm trying to make it easy but flexible for various use cases
A trip to Seattle would not be complete without bringing back some Chukar chocolate cherries 🍒
My first #MVPSummit was a blast! I had a lot of fun meeting so many nice people, and have the opportunity to provide feedback directly to Microsoft. I'm looking forward to next year already!
