New visuals and fluent design ✨ The Harden Windows Security module/app switches to .NET 9

[HotCakeX]

What's New

The Harden Windows Security now uses .NET 9 (PowerShell 7.5), that means:

• New appearance that is modern, based on Windows 11 fluent design
• Mica backdrop
• Better and more modern code
• Removal of all custom UI elements that belonged to the old WPF designs
• Faster startup time
• Support for light/dark theme in the OS
• Support for accent colors in the OS
• More accessible user experience
• Plus so much more benefits

Removed features:

• Custom background image.
• The ability to set custom background image.

Since Mica design is used for the background, there is no longer the need to set a custom color or custom background image.

PowerShell 7.5 was released 3 days ago, but since the module will require it, I'm waiting for PowerShell 7.5's MSIX package to be made available as well, and a day after that, will be releasing the new Harden Windows Security module version 0.7.4. This gives users enough time to install the new PowerShell version and also allows the bootstrapper script to automatically install the PowerShell 7.5 using MSIX package for users who don't have it.

This process ensures no downtime is experienced by users, especially those who use the Harden Windows Security module in automated workflows.

Copilot reviewed 85 out of 100 changed files in this pull request and generated no comments.

Files not reviewed (15)

• Harden-Windows-Security Module/.editorconfig: Language not supported
• Harden-Windows-Security Module/Harden Windows Security.csproj: Language not supported
• Harden-Windows-Security Module/Main files/.NETAssembliesToLoad.txt: Language not supported
• Harden-Windows-Security Module/Main files/C#/GUI/ASRRules/Variables.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/GUI/Confirm/Variables.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/Confirm Methods/InvokeConfirmation.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/GUI/Main/GUI.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/GUI/FileReputation/View.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/GUI/Log/View.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/GUI/ASRRules/View.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/GUI/Exclusions/View.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/GUI/AppControlManager/Variables.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/GUI/Confirm/View.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/GUI/AppControlManager/View.cs: Evaluated as low risk
• Harden-Windows-Security Module/Main files/C#/GUI/BitLocker/View.cs: Evaluated as low risk

[WildByDesign]

Fantastic work! I just wanted to say that I greatly respect and admire how fast you are to adopt the very latest technologies and how open you are to doing so. Keep up with doing awesome things! 💯

[HotCakeX]

@WildByDesign Thank you, appreciate it 🙏 I will!

I actually wanted to do this back in November but had to wait till PowerShell 7.5 is released to let me use .NET 9 features. My other app, AppControl Manager doesn't have this issue since I can always (and i do) use the most up to date .NET version and latest technology.