New icon

[jebeld17]

SharpKeys is in need of a new, modern icon.

(UPDATE: Please see below, along with Pull Request #186)

[jebeld17]

I put together a quick addition for the SharpKeys program as a brand new, modern icon, inspired by Fluent Design. Take a look below:

With that, SharpKeys also gets a new logo:

Other attachments:
Assets.zip

[jebeld17]

See Pull Request 186:
#186

[randyrants]

I had to close the PR because there's no way to make SharpKeys a Microsoft Store app; if you are interested in submitting a new logo, please work it into the Win32 codebase, which I think requires an ICO file.

Thanks!

[jebeld17]

My Pull Request did so and swapped out the .ICO file.
In addition, Microsoft now allows full-privileged Desktop Apps into the Microsoft Store.

[jebeld17]

See Pull Request #187

[randyrants]

The last meeting I went for this called out that while Win32 apps were supported there were still restrictions in place to protect critical parts of the system which included HKLM. I'll ask around on campus and see if that's still the case and check WACK. I started trying to get this into the Store 18 months ago, so it's not because I don't want it - it's because it wasn't supported.

[randyrants]

Sadly, the policy is unchanged: https://docs.microsoft.com/en-us/windows/msix/desktop/desktop-to-uwp-prepare

These three in particular:

• Your application always runs with elevated security privileges. - SharpKeys has to elevate itself to write to the Registry Key that Windows uses to remap things.
• Your application modifies the HKEY_LOCAL_MACHINE (HKLM) registry hive. - SharpKeys has to write to this hive because Windows does not respect any remapped keys when written to HKCU. It's been tried: doesn't work.
• Your application writes to the AppData folder or to the registry with the intention of sharing data with another app. - while SharpKeys isn't trying to put content in the Registry to share the data with other apps, Windows still needs to find the Value and there's no way it's looking in AppData.

Unless there's something that changed with VS 2019, this is the most recent information out there.