≈ the.bay.news

Licensing an MSIX-packaged Windows app

DEV Community
Licensing an MSIX-packaged Windows app
MSIX is how Windows desktop apps get installed now — through winget, through enterprise deployment, through the Store — and it quietly changes three things a licensing SDK depends on. Writes to %LocalAppData% are redirected into a per-package folder the app never sees in a path. Uninstalling the package deletes that folder, so the cached activation lease, the local trial clock and the clock-tamper state disappear while the seat on the licensing service stays bound. And the install directory is read-only, which is exactly where a bundled site license should sit. This post walks through what the Keyright SDK writes and where it lands under a packaged app, why the machine fingerprint survives when the cache does not, what an uninstall/reinstall cycle does to seat accounting (nothing, thanks to idempotent activation — unless the customer meant to move), how to detect package identity and give the SDK explicit paths, how to ship a license inside the package, when to disable write virtualization in the manifest, and the test loop that proves it.

0 comments

Sign in to join the discussion — your thebay.events account works here.

No comments yet.