none
[Desktop Bridge]No registry entries passed through using DesktopAppConverter RRS feed

  • Question

  • I have converted a standard MSI installer (for a Win32 application) using DesktopAppConverter and in general all goes fine and can be used through the MS Store. But our MSI installer contains some registry entries in HKEY_CURRENT_USER, but these are not installed by the appx. I can see a 'Registry.dat' file in the 'PackageFolder', so it looks like it has picked up something from the MSI installer.

    Is there a command line switch or something else that I have missed to use? Or perhaps this is not supported by the appx installer in the MS Store?

    Any advice is much appreciated.

    Mattias


    Friday, September 6, 2019 12:50 PM

Answers

  • Hi,

    In desktop bridge apps, all entries that your application writes to the HKEY_LOCAL_MACHINE registry hive are redirected to an isolated binary file and any entries that your application writes to the HKEY_CURRENT_USER registry hive are placed into a private per-user, per-app location. For example, if registry.dat contains a single key "Foo", then a read of HKLM\Software at runtime will also appear to contain "Foo" (in addition to all the native system keys). So you won't see the changes to the Registry because these changes happened on a isolated file.

    For more information, please refer:Prepare to package a desktop application and Behind the scenes of your packaged desktop application

    Best regards,

    Roy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by mpakarlsson Monday, September 9, 2019 9:47 AM
    Monday, September 9, 2019 2:45 AM
    Moderator

All replies

  • Hi,

    In desktop bridge apps, all entries that your application writes to the HKEY_LOCAL_MACHINE registry hive are redirected to an isolated binary file and any entries that your application writes to the HKEY_CURRENT_USER registry hive are placed into a private per-user, per-app location. For example, if registry.dat contains a single key "Foo", then a read of HKLM\Software at runtime will also appear to contain "Foo" (in addition to all the native system keys). So you won't see the changes to the Registry because these changes happened on a isolated file.

    For more information, please refer:Prepare to package a desktop application and Behind the scenes of your packaged desktop application

    Best regards,

    Roy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by mpakarlsson Monday, September 9, 2019 9:47 AM
    Monday, September 9, 2019 2:45 AM
    Moderator
  • Hi Roy,

    Thanks for the quick response and explanation.

    Thanks,

    Mattias

    Monday, September 9, 2019 9:47 AM