I think I found a bug with auto registration (AI 11.7), related to: http://www.advancedinstaller.com/forums ... =2&t=27883
Issue:
- Add a file (exe in my case) to the application folder.
- Enable auto registration on the file.
- Set to "Extract registration info from native library".
- Set synchronization to "Buildtime".
- Make sure this file's component is marked as 64-bit.
Result:
The component will be marked as 32bit in the resulting MSI, instead of 64bit. So, the registry entries will be made to the wrong location (32bit instead of 64bit). Sometimes this will be reflected in the AI interface (the "64-bit Component" checkbox), but usually not.
What I've noticed/tried:
- I've played around with UAC settings, no luck. I'm using a domain account that is an admin on the machine (Windows 7 64bit) .
- Setting synchronization to "Disabled" - the problem does not occur.
- Setting synchronization to "Enabled" - same problem occurs. I also noticed, if you restart AI, the component will no longer be marked as 64bit.
- Build times:
Setting synchronization to "Disabled" - 30 seconds to extract the registry info an put it into the project. 10 seconds to build the msi.
Setting synchronization to "Buildtime" - 2min 10 seconds to build the msi.
Not sure if this is relevant to the bug. Seems like using "Buildtime" takes longer than it should. Not sure how this scales with many files.
This bug, along with not having a "REG File To Merge At Build" feature, is making it difficult to handle lots of registry entries dynamically.
Thanks.
FOLLOW US
Get the latest news in Application Packaging