wix - Regasm installs shell extension correctly, but heat-generated WXS does not, writes to different registry path -


i wrote shell extension (item in explorer's file context menu), , used wix's heat create msi dll.

problem: installing msi not make context menu item appear.
in contrast, running regasm.exe my.dll /codebase makes item appear.

heat writes registry keys hkey_classes_root\, while
regasm writes registry keys hkey_local_machine\software\classes\.

i modify heat-generated wxs write same registry path regasm, msdn suggests hkey_classes_root , apparently users not able write hkey_local_machine... there better solution?

hkcr alias hklm\software\classes\ when msi package per-machine. easiest way ensure pre-machine package set installscope on package element:

<wix>   <product ...>      <package installscope='permachine' /> 

Comments

Popular posts from this blog

user interface - Python attempting to create a simple gui, getting "AttributeError: 'MainMenu' object has no attribute 'intro_screen'" -

jquery - Common JavaScript snippet to share files on Google Drive, Dropbox, Box.net or SkyDrive -

Android Gson.fromJson error -