Hello,
I have a synchronized folder where I have configured a few DLLs to auto register. After doing some work on other parts of our installer, we discovered that the installer no longer registered the configured DLLs. This was a mystery for some time, and our version control system got blamed for yielding merge errors, but I now believe I have found a bug in AI's handling of such files:
My theory: If you open the .aip file at a time where the synchronized folder does not contain one or more of the DLLs that are configured to register, they get lost in synchronization. Once you build your system and thereby fill the folder with those DLLs again, they are now updated as new files, without any special properties, like DLL registration. I expected any file with a special property set to be "remembered" by AI, so that any time they reappear in the folder, the same setting is reapplied. It is not.
My workaround seems to be to create a sub-folder that is not synchronized, put those DLLs in that folder and configure DLL registration on them, and then check "Install folder content into parent folder" on the synchronized folder. I guess I would have to filter those same DLLs out of the synchronized folder, to avoid conflicts or race conditions.
FOLLOW US
Get the latest news in Application Packaging