Description
Describe the bug
The AppIds used internal to the AppLifecycle feature are computing as a hash based on the executable path. The std::hash algorithms used on x86 and x64 builds are different and produce different outputs. This means filetype/protocol associations and instancing are incompatible on the same machine between and x86 and x64 variant of the same app.
example: I install the x86 version on accident and use it for a while, then realize I should use the x64 version. The app no longer tracks the same entries for associations and can't remove the old ones.
example: Both x86 and x64 version of the same app are installed, and they don't share instancing data and therefore can't coordinate which instance of the application handles different types of activations.
Steps to reproduce the bug
.
Expected behavior
No response
Screenshots
No response
IDE
Visual Studio 2019
NuGet package version
No response
Project type
- Packaged
- Unpackaged
Windows version
No response
Additional context
No response