Update 2:
But... 11.8 COM extraction with AI running under XP (the original subject of this topic) still does nothing.
I've added an improvement in our TODO list so we can use a consistent schema for all file paths added in "COM" page. We'll update this thread as soon as the improvement will be out. Thank you for your suggestion.I am concerned that the formatted references to the .exe and .ocx objects appear to be done differently on an object to object basis. In other words, two similar .ocx objects when subjected to COM extraction will produce different formatted path styles. In all, there are three different path styles produced by the extraction tool on our five objects. While they may all 'work' the result is disconcerting when trying to determine if the tool is working correctly.
Yes.Are you confirming that the /Automation switch has now been moved to the path field for .exe objects?
Indeed, the registry extraction still fails on Windows XP operating systems. I can confirm you this is still an Advanced Installer issue on which we are working. We'll try to add a fix in a future version of Advanced Installer and we'll let you know as soon as it will be out.But... 11.8 COM extraction with AI running under XP (the original subject of this topic) still does nothing.
Note that our registry data do not vary with the version of Windows or with Windows updates. It is the same on all versions of Windows. And it continues to work (unchanged) on all tested Windows platforms (XP, Win7, Win8x). As long as I don't attempt to perform an extraction, the existing AI projects work fine.Daniel wrote:It seems after applying latest Windows updates your COM files create/modify fewer registries on the systems when registered, therefore the API we use to extract the registration registries is catching fewer registration data. So, as long as the registration registry data of your COM files vary depending on the installed Windows updates, I'm afraid there is no improvement we can do.
I'm saying only that you cannot use our "Extract registration info from native library" option against COM files whose registration data vary after installing Windows Updates. I'm not sure why your COM files register less registration data on systems with Windows Updates up to date, but in this case I'm afraid it is not reliable to use our "Extract registration info from native library" option. This is a limitation of our COM registration tool and of the way it is implemented. We apologize for the inconvenience. All we do is to call the registration function within your COM files, fetch the create registration registries of your COM and then import them in the .aip (setup project) file.There is nothing to understand. Either complete registry data is extracted from executable objects by AI, or it is not. Are you saying that AI will never correctly extract registry data from .exe and .ocx COM objects generated by Embarcadero C++ Builder? If so, this is a potentially significant issue for anyone who is a using RAD Studio and your products.
Considering your particular COM files, I think the most straight-forward way to register your COMs would be to use a custom action. For example, you can call the regsvr32 tool within a custom action to register or unregister the COM files. You should use 3 custom actions for each of your COM file like this:What is the workaround? I would suggest that (as a minimum) you need to add a tool that that could import/export formatted .reg files so that one could at least export a working set of registry and COM entries from one project and import them into another project.
I've talked with our development team about corrupting registration registry on the build machine (hosting the AI), and indeed they admitted this may happen, but only when using EXE COM types in your setup project which are already registered on the build machine. If an EXE COM is already registered on the build machine, when using our option to extract the registration registries this is what could happen:It is your API that has problems. Not only does it not extract entries for Interfaces, but as of 11.9 it also corrupted the registry of our installed software on the computer that is hosting AI. I'm not sure how that is possible, given that your API should not be writing anything when it is reading data from our .exe and .ocx objects.
To avoid our registration limitations you can disable it and, then manually create from scratch the COM registration registries in our "Registry" page.Our issue is that if/when we need to make changes to our COM data, it becomes nearly impossible to update our AI projects. And hand creating COM and registry entries from scratch appears to be unsuccessful, due in part to the changes made recently to the structure of how COM info is stored in the AI projects. For example, AI insists on putting Interface registry entries under HKEY_LOCAL_MACHINE rather than under HKEY_CLASSES_ROOT when you edit an existing project. And that is not editable. Garbage gets left in the AI project file that has to be deleted by hand with a text editor.
As explained above our COM registration tool only triggers the COM file registration on current build machine, sniffs the registry data created by the registration process and, then unregister the COM files from the current build machine. What I meant was, we don't know why, but it seems your COM registration data is different when registering on machines having Windows updates up to date. This is why we recommended to use our COM registration option only on machines with a fresh copy of Windows installed.Daniel, our COM objects do not/can not self-register. So I do not understand what you mean when you say that they register different information under certain Windows updates. The information that your tool retrieves is incomplete and cannot be used. In addition, the AI interface attempts to put the Interface items in the wrong location in the registry.
I can assure you this is not a management issue, but a strictly technical one. We will try to fine tune our current COM registration option, but we cannot guarantee the lack of issues on special COM objects like yours are. We will clear this up in our Help files.Unfortunately, AI promised (pre-purchase) that this would be fixed. And then weeks became months, which became years as we waited for the promised fix because AI management decided that it was not a priority (or was too hard). Then, it worked -- for a couple of months (and only under Win7). And now, it is broken again and AI management seem to have decided that they do not want to spend any more time on this. Hindsight is 20/20.
The method we are using to gather the information from COM files is different than our competitors'. Our method indeed has some restraints, especially for some EXE files, as I previously explained. If you don't want to use the custom action approach I exposed in my previous post, then I'm afraid you should manually create the COM registration registries (sniffed with third party tools) in our "Registry"page.FYI, I just tested our current .exe and .ocx objects using our old InstallShield Express 2012 (under WinXP) to successfully extract COM info (at build time) and create an installer that runs successfully in Win7. Unfortunately, I cannot test a build under Win7 as our license does not permit me to move ISX to that platform.
Do we really have to keep a version of your competitors product around in perpetuity, using InstallShield Express to extract the COM data from our objects and then importing it into our AI projects so that we can reverse engineer this and fix it up in order to get it to work?
This may happen if you are trying to add a new type library (not interface) directly in our "COM" page. When adding from scratch a new type library in our "COM" page, it will be installed using the predefined Windows Installer "TypeLib" table which installs the type libraries into the HKEY_LOCAL_MACHINE registry location.The manual registration method that you mentioned, did not work for me. As mentioned previously, AI tries to put Interface entries under HKEY_LOCAL_MACHINE rather than under HKEY_CLASSES_ROOT. And this is not editable in the AI GUI (the option is greyed out).
No, this should not be an issue.You keep mentioning that our COM and EXE objects are registering different information under certain versions of Windows. Would this not also be an issue if we attempted to roll our own COM registration by using Regsvr32 run as a custom action?
I'm afraid we cannot test if the extracted registration info (caught by our COM extraction tool) is the proper one. This can be validated only by the COM's developer who authored the COM source files. As I said, all our "Extract registration info from native library" option does is to simulate the COM registration and sniff the registration data. To make sure the proper registration data was extracted you should test your installation package before releasing it. Also, this is a best practice which should be taken into account for all our features, not only for this specific ones.How is AI planning on handling this from a GUI and support perspective? While our company may be in the minority in still using legacy COM (for industrial automation) one would expect that the claimed support for Embarcadero RAD Studio and the presence of COM extraction tools in the AI GUI would indicate to a new user that this should work. Will you be making changes to your GUI to either disable COM extraction if Embarcadero project templates are selected? Or will your extraction tool put out a warning message if it senses an object that may fail? Partial extraction of COM data by AI tools has wasted a lot of our time and would no doubt waste other users time too.
FOLLOW US
Get the latest news in Application Packaging