GlenT
Posts: 118
Joined: Mon Jul 16, 2012 8:44 pm

COM extraction from .ocx .exe does nothing or is incomplete

Tried the 11.7 version which advertised COM extraction improvements. Was hoping that it was the fix for the problem that we reported more than 2 years ago, about AI failing (with an error message) to extract TLB COM info from our Embarcadero RAD Studio C++ Builder .exe and .ocx objects.

When I ran the extraction feature in AI 11.7, it no longer reports an error, but fails to do anything (no COM info stored in the AI project file under Registry). No registration was performed at install time.

Had to revert back to a project backup.

Edit: I have updated the title of the topic to reflect current issues.
Last edited by GlenT on Wed Mar 11, 2015 4:32 pm, edited 3 times in total.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: 11.7 COM extraction from .ocx .exe does nothing

Hello Glen,

I've tested an EXE file sent by you (two years and a half ago) against the "Extract registration info from native library" option and Advanced Installer extracted some registries which were added in our "COM" page. Can you please check the "COM" page and see if any registration entry has been added after enabling the above option for your COM file? You can check all extracted registries in "Registry" table from "Table Editor" page.

Also, can you send us to support at advancedinstaller dot com a download link for the related COM file(s) which are not registered after installation?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
GlenT
Posts: 118
Joined: Mon Jul 16, 2012 8:44 pm

Re: 11.7 COM extraction from .ocx .exe does nothing

The .exe that I sent you 2 1/2 years ago should be essentially the same as our current one. No COM changes have been made and we are still using the same version of RAD Studio 2010 for distribution/production.

When I tested this, I manually deleted all of the entries on the COM page (which had been imported from InstallShield Express). Then I performed the extraction, updated the AI project and checked the COM page. There were no entries. Then I built an installer and ran it. COM was not enabled on the application or its associated .ocx objects, so it was not just a matter of AI having failed to update the COM page.
GlenT
Posts: 118
Joined: Mon Jul 16, 2012 8:44 pm

Re: 11.7 COM extraction from .ocx .exe does nothing

I just tried this with a brand new AI project, and it also failed to extract anything from CSPlus.exe. Note, that I don't think I have the Table Editor features. We use AI Professional.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: 11.7 COM extraction from .ocx .exe does nothing

Hello Glen,

Can you please send us a download link for your "CSPlus.exe" file to support at advancedinstaller dot com so we can test and investigate it?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
GlenT
Posts: 118
Joined: Mon Jul 16, 2012 8:44 pm

Re: 11.7 COM extraction from .ocx .exe does nothing

OK, will do. However, I don't see how it will be any different than the file that you already have.

I want to confirm that you are performing the same test that I am:

Import the .exe file into a new AI project. Right-click on the file in Files and Folders view and click Properties. Click the Registration tab. Tick the box beside Auto Register file. Click the radio button beside 'Extract registration info from native library'. Click the OK button. Update the AI project file. Check the COM tab for new entries under all four categories (none in my case). Exit AI and open the .aip project file with a text editor. search for CLSID entries (none in my case).

If you are doing something different to get a different result, then please let me know.

P.S. Not sure if this is relevant or not, but I am currently running AI under Windows XP.
GlenT
Posts: 118
Joined: Mon Jul 16, 2012 8:44 pm

Re: 11.7 COM extraction from .ocx .exe does nothing

Further information:

On a hunch, I tried this under Windows 7 Pro 64bit and AI succeeds, but not completely. A couple of key registry entries are missing from the list, but it does succeed in finding most of them.

So, to recap, doesn't work at all when AI is running under WIndows XP 32bit. Works, but not completely, under Windows 7 Pro 64bit.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: 11.7 COM extraction from .ocx .exe does nothing

Hello Glen,

I've tested the scenario using your sent files and, indeed I can replicate the behavior. I've opened a task in our bug tracking system so that our development team analyze and investigate this issue. I'll get back to you as soon as we have a resolution.

Thank you for your patience and understanding.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
GlenT
Posts: 118
Joined: Mon Jul 16, 2012 8:44 pm

Re: 11.7 COM extraction from .ocx .exe does nothing

OK, thanks. Will look forward to that.

Note that there are two problems. One is that it doesn't run under XP. The other is that entries for the .exe files are not complete.
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: 11.7 COM extraction from .ocx .exe does nothing

Hi Glen,

An improvement regarding this issue has been added in the 11.8 version of Advanced Installer released on January 28th, 2015.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
GlenT
Posts: 118
Joined: Mon Jul 16, 2012 8:44 pm

Re: 11.7 COM extraction from .ocx .exe does nothing

Thanks, Dan. Will give it a try and let you know.
GlenT
Posts: 118
Joined: Mon Jul 16, 2012 8:44 pm

Re: 11.7 COM extraction from .ocx .exe does nothing

So far, 11.8 does not look encouraging for COM extraction. The good news is that it is doing something with .exe and .ocx objects, which looks better for COM and Type Library categories. And so far, it does seem to be working.

The bad news is that other stuff is changed or missing:

1. No Interfaces information is visible on the COM page (this was working in v11.7) after Extract registration info from native library
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?
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.
4. Properties > Regisration > Synchronization > Buildtime does nothing and leaves empty folders under COM.

All testing was done under Win7 Pro.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: 11.7 COM extraction from .ocx .exe does nothing

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
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
GlenT
Posts: 118
Joined: Mon Jul 16, 2012 8:44 pm

Re: 11.7 COM extraction from .ocx .exe does nothing

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.

Are you confirming that the /Automation switch has now been moved to the path field for .exe objects?

Again, I recently sent you current versions of our five objects. I try building up a new self-contained test sample and send it to you if it fails to display Interfaces info. Note that I believe that the interfaces info may be there, but I need to see it to verify that the tool is actually succeeding.
GlenT
Posts: 118
Joined: Mon Jul 16, 2012 8:44 pm

Re: 11.7 COM extraction from .ocx .exe does nothing

Update:

I successfully created a new project and extracted COM info from all five objects under Win7. The info seems complete and the paths are consistent.

I then went back to my production project and deleted all references to the .exe and .ocx objects. I deleted the COM entries, files, and all registry entries that appeared under HKEY_CLASSES_ROOT in the AI project file.

I then re-added the five .exe and .ocx objects, performed the extractions and repaired the shortcuts and File Associations. Now everything seems to work and the paths to the objects are consistently formatted. Under testing, so far, everything seems to be working when running AI under Win7.
Last edited by GlenT on Thu Jan 29, 2015 7:58 pm, edited 1 time in total.

Return to “Common Problems”