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: Upgraded InstallScript project compile error
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 17, 2011
02:11 PM
Upgraded InstallScript project compile error
I'm trying to get all our old IS 10.5 projects upgraded to IS 2011.
I have one Installscript project that ran through the conversion but when I compile the script I get the following error.
-----
InstallShield Script Compiler
Version 17.0.0.714
Copyright 1997-2010 Flexera Software, Inc. and/or InstallShield Co. Inc. All Rights Reserved.
Compiling...
setup.rul
Linking...
C:\Projects\TFS\FGM\Main\ProductInstall\WorkPacketManager\InstallShield10\Script Files\iswi.obl : fatal error F8522: The system cannot find the file specified.
------
I've looked through the knowledgebase and community articles but find nothing that indicates what the problem might be.
This is a purely Installscript project.
The IS help says that it automatically finds ifx.olb and Isrt.olb for InstallScript and InstallScript Object projects.
It says that it automatically finds iswi.olb and isrt.olb for Basic MSI and InstallScript MSI projects.
If this is an Installscript project, why is it looking for iswi.olb?
I can get it to compile by setting the Additional Library Paths (in Build/Settings) to "Script\Iswi\Lib" but I'm concerned that that might have some subtle, unintended, side affect.
Can anyone give me a clue as to why iswi.olb might be required by this converted Installscript project?
Richard
I have one Installscript project that ran through the conversion but when I compile the script I get the following error.
-----
InstallShield Script Compiler
Version 17.0.0.714
Copyright 1997-2010 Flexera Software, Inc. and/or InstallShield Co. Inc. All Rights Reserved.
Compiling...
setup.rul
Linking...
C:\Projects\TFS\FGM\Main\ProductInstall\WorkPacketManager\InstallShield10\Script Files\iswi.obl : fatal error F8522: The system cannot find the file specified.
------
I've looked through the knowledgebase and community articles but find nothing that indicates what the problem might be.
This is a purely Installscript project.
The IS help says that it automatically finds ifx.olb and Isrt.olb for InstallScript and InstallScript Object projects.
It says that it automatically finds iswi.olb and isrt.olb for Basic MSI and InstallScript MSI projects.
If this is an Installscript project, why is it looking for iswi.olb?
I can get it to compile by setting the Additional Library Paths (in Build/Settings) to "
Can anyone give me a clue as to why iswi.olb might be required by this converted Installscript project?
Richard
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 19, 2011
01:01 PM
Generally speaking, iswi.obl should not be included in an InstallScript project since it overrides a number of events with code specific to InstallScript MSI projects (and other MSI specific functions exposed through to InstallScript).
Does the project have a reference to iswi.obl prior to upgrading to IS 2011?
Does the project have a reference to iswi.obl prior to upgrading to IS 2011?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 19, 2011
01:06 PM
I could find no reference in the old version. In fact I wouldn't have known to even look for it until this error occured.
Do you know what, in the project definition, triggers the inclusion? If I knew that I might be able to eliminate it.
Richard
Do you know what, in the project definition, triggers the inclusion? If I knew that I might be able to eliminate it.
Richard
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 19, 2011
01:19 PM
NEVERMIND - I found it.
I went back and looked again. The old version included iswi.olb in the Build>Settings...>Compile/Link.
Apparently the IS 10.5 compiler didn't care about that.
I removed iswi.olb from the libraries and it Compiled just fine.
My apologies for the stupid question. Sometimes you just have to walk away and then come back to see something that is staring you in the face the whole time.
Richard
I went back and looked again. The old version included iswi.olb in the Build>Settings...>Compile/Link.
Apparently the IS 10.5 compiler didn't care about that.
I removed iswi.olb from the libraries and it Compiled just fine.
My apologies for the stupid question. Sometimes you just have to walk away and then come back to see something that is staring you in the face the whole time.
Richard
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 19, 2011
01:34 PM
There were some changes to how library paths were handled in IS 2010, so that may account for the change in behavior. If the project builds fine without the iswi.obl library though, it is best to just remove any reference to it.