ALIENQuake

The `C:\ProgramData` was recently dropped by Git for Windows team due to the amount of confusion it creates: https://github.com/git-for-windows/git/pull/2358 Let's forget about this directory once for all.

@SeeminglyScience The `.Ast.GetScriptBlock()` ❤️

@hongwen000 My workaround is: - have PSScriptAnalyzerSettings.psd1 file inside your GitHub repo - clone the repo locally into your user profile/Documents directory - create C:\Users\Public\PSScriptAnalyzerSettings.psd1 as a Symbolic Link into...

@hongwen000 Nr 2 😃

Same issue: no data if I weave appcenter+dependencies into the main assembly via Fody/Costura. I cannot use Net Core PublishSingleFile.

@daxian-dbw FWIW, I'm facing this issue using SAPIEN PowerShell Studio.

@wi-fr Hi, see https://github.com/PowerShell/PowerShell/issues/18414#issuecomment-1298307465 > > I cannot reproduce the problem, PowerShell updated to 7.3.0-rc.1: > ``` > using namespace System.Diagnostics > using namespace System.Windows > using namespace System.Windows.Controls >...

I also was able to reproduce this on my Surface Pro using the x64 MSI package. It works using 'PowerShell-7.3.0-rc.1-win-fxdependentWinDesktop' package with the installed required NET 7 RC2.

I'm very interested in having this feature. @fMichaleczek Hi, The 'true single file' feature (without fallback to IncludeNativeLibrariesForSelfExtract) depends on .NET Core 'SuperHost' feature. For Net Core version 5.0 this...

When it comes to 'PS-based' single executable tools, the advantages of the "single file" approach are that the executable bounds NET version and PSVersion so the produced tool will work...