René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Windows: WinForms and WPF assemblies are missing from the ARM64 builds","articleBody":"### Prerequisites\r\n\r\n- [X] Write a descriptive title.\r\n- [X] Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)\r\n- [X] Search the existing issues.\r\n- [X] Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).\r\n- [X] Refer to [Differences between Windows PowerShell 5.1 and PowerShell](https://docs.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell).\r\n\r\n### Steps to reproduce\r\n\r\n_Update_: The problem is specific to Windows ARM64 builds, irrespective of installation method - see [below](https://github.com/PowerShell/PowerShell/issues/18858#issuecomment-1366298974)\r\n\r\n~~Whether the WinForms and WPF assemblies ship with PowerShell Core depends on the installation method~~:\r\n\r\n* ~~YES:~~\r\n    * ~~MSI package~~ [the only reason this worked is because I accidentally installed the x64 version, not the ARM64 one]\r\n* ~~NO~~:\r\n    * ~~`winget install Microsoft.PowerShell` (Microsoft Store)~~\r\n    * ~~Installation via https://aka.ms/install-powershell.ps1~~\r\n\r\nThus, WinForms code breaks ~~with the latter two installation methods~~ with ARM64 builds, because~~ `Add-Type -AssemblyName System.Windows.Forms` fails due to the absence of the relevant assemblies.\r\n\r\n  * Note:  The .NET Framework version in the GAC is _not_ found, though loading it explicitly with `Add-Type -LiteralPath C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\System.Windows.Forms.dll` does seem to work in practice.\r\n\r\nVerify the presence / absence with:\r\n\r\n ```powershell\r\nGet-Item $PSHOME/System.Windows.Forms.dll\r\n```\r\n\r\n~~Is this a known / by-design? If so, it should at least be documented, with a detailed list of what's absent when not using the MSI installer.~~\r\n\r\n---\r\n\r\nNote that there's also technically distinct, but related problem (which also happens if the WinForms assemblies _are_ present): the ability to load the WinForms assembly via  `using assembly System.Windows.Forms` has been broken since using  before v7..0:\r\n * see https://github.com/PowerShell/PowerShell/issues/11856\r\n\r\n\r\n\r\n\r\n### Expected behavior\r\n\r\nThe file should be present.\r\n\r\n\r\n### Actual behavior\r\n\r\nThe file is present only if PowerShell was installed via the MSI installer\r\n\r\n\r\n### Error details\r\n\r\n_No response_\r\n\r\n### Environment data\r\n\r\n```powershell\r\nPowerShell Core v7.3.1 (.NET 7.0.0)\r\nPowerShell Core v7.4.0-preview.1 (.NET 7.0.1) \r\non Microsoft Windows 11 Pro (ARM 64-bit Processor; Version 22H2, OS Build: 22621.963)\r\n```\r\n\r\n\r\n### Visuals\r\n\r\n_No response_","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2022-12-27T22:42:59.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":12},"url":"https://github.com/18858/PowerShell/issues/18858"}