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: .NET COM Interop not working in IS 2008?
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
Feb 13, 2008
04:08 PM
.NET COM Interop not working in IS 2008?
We have an IS 12 Basic MSI project that we've converted to IS 2008 to improve Vista deployment and the first thing we've noticed is that our .NET dlls are no longer being registered for COM Interop.
We haven't touched the properties of the components (.NET Scan at Build = Properties Only, .NET Com Interop = Yes) and have also noticed that a reg file is no longer created alongside the source dll (which it used to be in IS 12) and nothing is mentioned in the build log about extracting the reg data via regasm - errors or otherwise. I've also confirmed that the .NET 2.0 regasm.exe is in the usual place and that the IS 2008 options has the correct location configured for the Framework directory.
The only other change is that the dlls are now .NET 2.0 rather than 1.1, but the dlls register fine using regasm on the target system - just not when deployed using IS 2008.
Has this process changed or been broken in IS 2008?!
Many thanks,
James
We haven't touched the properties of the components (.NET Scan at Build = Properties Only, .NET Com Interop = Yes) and have also noticed that a reg file is no longer created alongside the source dll (which it used to be in IS 12) and nothing is mentioned in the build log about extracting the reg data via regasm - errors or otherwise. I've also confirmed that the .NET 2.0 regasm.exe is in the usual place and that the IS 2008 options has the correct location configured for the Framework directory.
The only other change is that the dlls are now .NET 2.0 rather than 1.1, but the dlls register fine using regasm on the target system - just not when deployed using IS 2008.
Has this process changed or been broken in IS 2008?!
Many thanks,
James
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 14, 2008
11:53 AM
To get regasm to work on my .dlls I have had to set the COM extract at Build property to YES and set the .NET COM interop property to YES. See if that works for you.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)