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
- :
- Installing stdole.dll to GAC
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
May 29, 2009
08:30 AM
Installing stdole.dll to GAC
Hi, I'm trying to install stdole.dll to GAC with Installshield 2009. As far as I know this is not a .NET assembly so I've set my component to ".NET Scan at Build" to "None". Target is [GlobalAssemblyCache].
But the file is never installed to GAC and it doesn't show up using "gacutil.exe /l".
If I manually use "gacutil.exe /i stdole.dll" it's installed and shows up in list. I guess I could shell the instruction in a script but I rather use the default facilities in InstallShield.
I've also tried setting the ".NET Scan at Build" property to "Properties Only" but I get this:
http://brn.ath.cx/img/Properties.only.stdole.dll.jpg
What can I do to force the installation ?
But the file is never installed to GAC and it doesn't show up using "gacutil.exe /l".
If I manually use "gacutil.exe /i stdole.dll" it's installed and shows up in list. I guess I could shell the instruction in a script but I rather use the default facilities in InstallShield.
I've also tried setting the ".NET Scan at Build" property to "Properties Only" but I get this:
http://brn.ath.cx/img/Properties.only.stdole.dll.jpg
What can I do to force the installation ?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 03, 2009
07:03 AM
Somehow I was able to solve this by deleting the component and making a new one. Possibly because that also gave me a new GUID.
".NET Scan at Build" property set to "Properties Only".
I'm not sure what it is IS actually does scanning for .NET assemblies. Maybe it doesn't work because I have more than one non-.NET dll in that component. If so I can add a new component for every file and set it as "key file".
".NET Scan at Build" property set to "Properties Only".
I'm not sure what it is IS actually does scanning for .NET assemblies. Maybe it doesn't work because I have more than one non-.NET dll in that component. If so I can add a new component for every file and set it as "key file".