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: Error -6210: An error occurred building COM .NET Interop information for Component
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
‎Aug 26, 2009
11:22 AM
Error -6210: An error occurred building COM .NET Interop information for Component
Hi,
I am getting this error when setting the .Net COM Interop to yes on a component that is .Net.
Furthermore, when running RegAsm.exe on this .net Dll the registration is successful.
Please let me know if anyone else has faced this problem and have a solution to it.
Thanx,
Y.
I am getting this error when setting the .Net COM Interop to yes on a component that is .Net.
Furthermore, when running RegAsm.exe on this .net Dll the registration is successful.
Please let me know if anyone else has faced this problem and have a solution to it.
Thanx,
Y.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 18, 2009
05:42 PM
I am struggling with the same problem right now, can you post your solution once you have it? I will do so too if I figure it out.
Thanks,
PB
Thanks,
PB
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 21, 2009
06:57 PM
FYI, I am registreing a .dll which should not be, by mistake. Once I remove that one, installshield builds fine with all the other ones.
Y., if you are not the developer of the assemblies (that's my case), you might want to talk with the developer(s) about this and ensure that the assemblies SHOULD be registered.
Y., if you are not the developer of the assemblies (that's my case), you might want to talk with the developer(s) about this and ensure that the assemblies SHOULD be registered.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)