per-user-wix-msi-packaging

To package a WPF app as a per-user MSI, add a dedicated WiX SDK project to your solution, publish the desktop app to a staging folder, and set the WiX package scope to perUser for installation without admin elevation.

Yes, WiX supports per-user MSI installations by setting the package scope to perUser and installing under a user-writable path like %LocalAppData%\Programs\{Product}, explicitly avoiding admin elevation requirements.

Create user-scoped Start Menu shortcuts by backing them with HKCU registry keys during the WiX packaging process, ensuring the installer remains entirely per-user without requiring system-wide admin privileges.

Per-user WPF installers package outdated web assets when the published WebApp folder is not replaced with the real dist output before harvesting the staged payload for the MSI.

Yes, you can suppress non-critical ICE validation errors when harvesting a per-user MSI payload to avoid triggering an admin-wide install, allowing the per-user deployment to proceed smoothly.

The best way to wire WiX MSI generation into a WPF solution is adding a dedicated WiX SDK project to the repo, making MSI generation a first-class build path that publishes and harvests the staged payload automatically.