For DLL (and EXE) custom actions, the bitness is determined by the action's
binary itself, not any marking in the MSI. In the case of DTF, the initial
bitness employed will be the bitness of the sfxca.dll packaged by the
wrapping action of the DTF build process. I haven't looked at the source
code
Good to know for future reference as I have take Blair's good advice and no
longer fool with CA's to touch the registry or the event source and do those
with wix elements. My only custom action left decodes a des256 string to get
credentials for when I create the service and that works well.
2 matches
Mail list logo