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
- :
- Install Issue
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
‎Jan 31, 2010
12:09 AM
Install Issue
Hi
I am having a problem with Install Shield setup installation in Windows7. I need to place a DLL in GAC during my installation. I set key for my DLL and setup built successfully. When I am installing I got the below error.
"The assembly is not strongly named or is not signed with the minimal key length"
Any suggestions to solve this error are highly appreciated.
I am having a problem with Install Shield setup installation in Windows7. I need to place a DLL in GAC during my installation. I set key for my DLL and setup built successfully. When I am installing I got the below error.
"The assembly is not strongly named or is not signed with the minimal key length"
Any suggestions to solve this error are highly appreciated.
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 31, 2010
05:11 AM
Can you drag the assembly into the GAC manually? ( Open windows explorer to [WindowsFolder]\Assembly and drag it in. )
It sounds like your assembly isn't properly strong named.
It sounds like your assembly isn't properly strong named.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 03, 2010
08:43 AM
There's a property in the installshield component called .NET Com Interop. Set it to Yes.
Mind you I've never had a reason to put an assembly in the GAC and make it COMVisible. Something sounds off there and I'm not really sure that it'll work. You might want to deploy the file to CommonFiles as I'm not 100% positive that registering the COM types and pointing the codebase attribute to the GAC will work or not.
Mind you I've never had a reason to put an assembly in the GAC and make it COMVisible. Something sounds off there and I'm not really sure that it'll work. You might want to deploy the file to CommonFiles as I'm not 100% positive that registering the COM types and pointing the codebase attribute to the GAC will work or not.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 03, 2010
10:17 AM
Hi
I already tried to set the .NET Com Interop property to yes and deployed in a system. But I was unable to find it in VBA project references. Any other suggestions from your side.
Earlier I used to deploy this DLL using .Net setup. At that time I configured this assembly with VSDRCom option. You can see it in below attachment.
I already tried to set the .NET Com Interop property to yes and deployed in a system. But I was unable to find it in VBA project references. Any other suggestions from your side.
Earlier I used to deploy this DLL using .Net setup. At that time I configured this assembly with VSDRCom option. You can see it in below attachment.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 03, 2010
10:18 AM
Here is the attachment.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)