[PowerToys Run] Upgrade .NET Core 3.1 to .NET 5

[mykhailopylyp]

Description of the new feature / enhancement

Upgrade PowerLauncher and all plugins to .NET 6

PowerToys Run and some plugins use Windows Runtime. It is not available in .NET 5 as before but can still be used with Target Framework Moniker option. With this option we have to specify the version of windows runtime. It should be windows10.0.18362.0 as it is the lowest version of windows we support. We should explorer other options here as well.

There is a bunch of obsolete APIs that should be replaced:

• Assembly.GlobalAssemblyCache. It is used in exception formatted to show loaded assemblies. Should be easy to fix
• Microsoft.Toolkit.Uwp.Notifications.NotificationActivator. It is used for toast notifications
• Microsoft.Toolkit.Uwp.Notifications.DesktopNotificationManagerCompat. It is used for toast notifications
• System.Runtime.Serialization.Formatters.Binary.BinaryFormatter

[mykhailopylyp]

Parent issue is #8650

[davidegiacometti]

@mykhailopylyp
with Microsoft.Toolkit.Uwp.Notifications removed registry key can also be removed.

PowerToys/installer/PowerToysSetup/Product.wxs

Line 1073 in e762bfa

<RegistryKey Root="HKLM" Key="SOFTWARE\Classes\AppUserModelId\PowerToysRun">

Reference: https://docs.microsoft.com/en-us/windows/apps/design/shell/tiles-and-notifications/send-local-toast?tabs=desktop#step-4-handling-uninstallation

[dedavis6797]

@DHowett shouldn't we be in a good state to get this done next release with the build pipeline migration just about wrapped up?

[DHowett]

Yeah.

[crutkas]

This needs the new pipeline work before we can migrate so moving to 0.55

[crutkas]

@stefansjfw is this work done with the .net 5 upgrade?

[stefansjfw]

@crutkas yes