This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: How can I make IS use the 64-bit version of RegAsm for self registering COM DLL?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 28, 2014
01:53 PM
How can I make IS use the 64-bit version of RegAsm for self registering COM DLL?
System spec:
- Install Shield 13 Limited Edition
- Visual Studio 2012
- Windows 8 64-bit
I have a self registering COM DLL. Building the MSI package for 32-bit goes fine and RegAsm correctly registers the DLL after I install this MSI package. To make a 64-bit build, I change my DLL project to type Platform Target: 64-bit in hope that InstallShield will use the 64-bit path for RegAsm. But it seems to use the 32-bit .NET path which causes the MSI to not register the DLL correctly. I noticed it uses the 32-bit path because when I change the 64-bit path to some dummy path, it does not complain, while if I change the 32-bit path to a dummy path, it does complain.
How can I make InstallShield use the 64-bit version of RegAsm? How does InstallShield determine if it should use the 32 or 64 bit path for .NET?
I found in documentation that there is a "Template Summary Property" that can be set to x64 which might make InstallShield treat register my DLLs with 64-bit version of RegAsm. However, I cannot find this "Template Summary Property" anywhere in the settings.
Attached log file from my IE build if needed.
Would really appriciate if you could help me with this.
- Install Shield 13 Limited Edition
- Visual Studio 2012
- Windows 8 64-bit
I have a self registering COM DLL. Building the MSI package for 32-bit goes fine and RegAsm correctly registers the DLL after I install this MSI package. To make a 64-bit build, I change my DLL project to type Platform Target: 64-bit in hope that InstallShield will use the 64-bit path for RegAsm. But it seems to use the 32-bit .NET path which causes the MSI to not register the DLL correctly. I noticed it uses the 32-bit path because when I change the 64-bit path to some dummy path, it does not complain, while if I change the 32-bit path to a dummy path, it does complain.
How can I make InstallShield use the 64-bit version of RegAsm? How does InstallShield determine if it should use the 32 or 64 bit path for .NET?
I found in documentation that there is a "Template Summary Property" that can be set to x64 which might make InstallShield treat register my DLLs with 64-bit version of RegAsm. However, I cannot find this "Template Summary Property" anywhere in the settings.
Attached log file from my IE build if needed.
Would really appriciate if you could help me with this.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 30, 2014
01:44 PM
Hi dohodoho,
"Template Summary Property" is not exposed in Limited Edition. When you add a file or registry to the 64-bit location, the install should automatically becomes 64-bit.
Where is the dll getting installed to?
"Template Summary Property" is not exposed in Limited Edition. When you add a file or registry to the 64-bit location, the install should automatically becomes 64-bit.
Where is the dll getting installed to?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 02, 2014
06:55 AM
kyi wrote:
Hi dohodoho,
"Template Summary Property" is not exposed in Limited Edition. When you add a file or registry to the 64-bit location, the install should automatically becomes 64-bit.
Where is the dll getting installed to?
I think only the professional supports 64-bit COM installations. The DLL is installed to the C:\Users\username\AppData\Local\productname\
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 17, 2015
03:50 PM
The newest version of IS LE should support x64 installations. Is that limited to locations? Or would IS LE 2013 support the correct version of regasm? I am trying to migrate from a vdproj that worked perfectly.
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)