Hello Glen,
1. No Interfaces information is visible on the COM page (this was working in v11.7) after Extract registration info from native library
Can you send us a download link for a file which replicates this behavior? I've tested all files (EXE and OCX) that you already sent us, but I cannot replicate the behavior. It would be very useful if you could isolate the behavior in a buildable sample and send it us alongside a test case scenario.
2. The Options section of the Class page is now entirely missing. /Automation now seems to appear at the end of the File field instead of in the Options section. Is this a change?
Yes, currently this is our default behavior when using the "Extract registration info from native library" registration option.
3. I get varied results as to Path information for the COM objects. Some paths appear (correctly?) as APPDIR\BIN\object.ocx. Others appear to have the local folder [PersonalFolder]Local Path\object.ocx. For .exe files, I see [#CSPlus.exe] /Automation instead of APPDIR\BIN\CSPlus.exe. What does the # sign mean? Sometimes the Details Directory has a local path rather than a target path. The Help has not been updated as to what is happening with this, so not sure what is correct nomenclature.
All of the above are correct paths. The "[#CSPlus.exe]" is a
formatted reference of your EXE file which will be resolved at install time to the EXE full path.
4. Properties > Regisration > Synchronization > Buildtime does nothing and leaves empty folders under COM.
Yes, this is our current implementation. When the synchronization is set to be done at build time, the registration registries will be extracted only at build time and included in the MSI file. Afterwards, they won't be shown neither in "Registry" page nor in "COM" page.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging