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: An error occurred building COM .NET Interop information for Component ExriExtensionFi
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 27, 2012
02:10 PM
An error occurred building COM .NET Interop information for Component ExriExtensionFi
Hi to all,
first thanks for read this post.
The company where I work upgrade to installshield 2012, but now the installer build launch the next exception:
ISDEV : error -6210: An error occurred building COM .NET Interop information for Component ExriExtensionFiles
The Installshield project was auto migrated for Installshield without problems.
Someone recognizes this error?
first thanks for read this post.
The company where I work upgrade to installshield 2012, but now the installer build launch the next exception:
ISDEV : error -6210: An error occurred building COM .NET Interop information for Component ExriExtensionFiles
The Installshield project was auto migrated for Installshield without problems.
Someone recognizes this error?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 01, 2012
04:15 PM
The .NET COM interop functionality in IS 2012 was updated to use the new COM extraction functionality to allow for greater flexibility in acquiring COM interop information. However, if for some reason COM extraction failed to run or extract any data, this error could occur.
Are there any other assemblies in this project that also use .NET COM interop? Do these successfully acquire COM interop information? Can you reproduce this behavior in a sample project with the assembly in this component? If so, would it be possible for you to send us the project?
Note that you can use the old COM extraction and .NET COM interop functionality by changing the COM extraction method used by InstallShield (search the help for UseAPIRegistryHooks for more information).
Are there any other assemblies in this project that also use .NET COM interop? Do these successfully acquire COM interop information? Can you reproduce this behavior in a sample project with the assembly in this component? If so, would it be possible for you to send us the project?
Note that you can use the old COM extraction and .NET COM interop functionality by changing the COM extraction method used by InstallShield (search the help for UseAPIRegistryHooks for more information).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 01, 2012
09:08 PM
You can also run regasm /regfile:test.reg on the assembly and then import the reg file into your component.