ISCmdBld.EXE 2009 action missing -o option

FinalBuilder Bugs
1

We are in the process of switching from InstallShield 12 to InstallShield 2009.  Our builds are failing because the newly built merge modules are not being copied to merge module location as specified by the first folder in the "Merge Module Path" field of the Stand Alone tab of the action.  The help says

"Merge Module Path : Enter a single path or multiple comma separated paths to the merge modules.  You will need to manually quote this field if you are entering multiple paths (individually quoted) or your path contains spaces. The first path is what is selected as the path to copy the MSM file.

Note:

The copy will only work if IsSABld.exe is set as the IS executable. This is because it has the -o option w/in InstallShield"

 

However, the merge modules are not being copied.    In IS 2009 Stand Alone Build Tool, it appears that IsSABld.exe IS NO LONGER installed as part of the tool.  However, IsCmdBld.exe IS installed as part of the tool.  And, in deed, Tools->Options-->Install Builders-->InstallShield--> InstallShield 2009 Location is populated with \System\IsCmdBuild.exe.

After creating an IS 2009 project action and populating it with the settings from a previous IS 12 project action, it fails to copy the .MSM to the specified Merge Module folder.  And, the FinalBuilder log file showing the command issued does NOT have the -o option specifying the merge module path.  But, when running the exact command from the command line with the -o included, everything works as it used to. 

So, is this something that can be looked into and fixed quickly?

 Also, is there a way to "upgrade/convert" one action to another?  In this case, convert an "Installshield Dev7+,X+,11,12 Project (MSI)" action to an "InstallSheild 2009 Project" action?  Say, right click on the current action and have the ability to select convert to either IS2008 Project action or IS2009 Project action and have all of my current settings ported over?

 

BTW, I'm using FinalBuilder 6.1.0.891.

Thanks in advanced for your help guys!!!

 

Regards,

Tracey

2

Hi Tracey,

I believe this has already been addressed. Please try this build:
https://www.finalbuilder.com/downloads/finalbuilder/610/FB610_937.exe

re: upgrade/convert - sorry, that’s quite a task for us to do and we currently have more urgent priorities.

3

We here have done installshield package generation using different kind of approach. If you have problems using FB’s own installshield action, you could try what we’re using (this is for installshield 2008’s stand alone builder, but should work with installshield 2009 as well):

make_installshield_package.bat :

IF %1 == “” GOTO BROKEN

set MERGE_MODULE_PATH="…\MergeModule","%programfiles%\Common Files\Merge Modules"

“%programfiles%\Macrovision\IS 2008 StandaloneBuild\IsSABld.exe” -p “projectx_is2008_version.ism” -a PROJECT_ASSISTANT -r “%1” -x -o %MERGE_MODULE_PATH% -b c:\temp\packagedir
IF %ERRORLEVEL% NEQ 0 GOTO BROKEN
GOTO END

:BROKEN
EXIT 1

:END


PS: Notice that I’ve deliberately defined the output directory to c:\temp\packagedir (using -b switch). This is to overcome the path length ristrictions of 255 chars of ISB (installshield standalone builder).

PS2: the batch file should be called with parameter - the parameter is passed to the ISB command line, and it’ll determine the name of the release to be built.

Arsi

4

Thanks for the quick response.  I'm going to give it a try and let you know something by the end of the day.

BTW, I didn't really expect to get a convert action but thought it didn't hurt to ask! 

Regards,
Tracey

5

Downloaded and tested FB610_937.exe.  Works like a charm! 

Thanks Guys!!!

-->Tracey-

6

cool - thanks for confirming

7

Hello

I know you guys were busy working on other things, but I’d like to know how to formally request that an upgrade/conversion tool or action be added for upgrading previous Installshield actions to newer ones? The reason I ask this is because it is quite PAINFUL to have to MANUALLY REPLACE each and every Installshield action in every FinalBuilder project whenever we upgrade our Installshield toolset.

It was really MUCH EASIER when all of the Installshield actions were consolidated into ONE action and didn’t really matter which version I was running as long as I’d configured the InstallShield Location.

PLEASE look into making life easy again…

Regards,
Tracey

8

Hi Tracey

We’re looking into this. I believe I have found a way to merge the existing actions while maintaining backwards compatibility. Hopefully we should have something to show next week.

9

-->Tracey

10

Hi Tracey

Here is a build where the InstallShield Dev, 2008, 2009 & 2010 actions have been merged. Please be sure to back up your projects before installing this build. Once a project is saved with this build, whilst it will still load in older version of FB, the installshield actions will all be for IS2010.

https://www.finalbuilder.com/downloads/finalbuilder/630/FB630_1756.exe

Note that on the IS action you will need to select the Installshield version. The merged action should hopefully set it correctly when the project is loaded, however please check that it has done so correctly.

NOTE for other users : Do not be tempted to install this build unless you a) want to test the new Installshield action, or b) do not use Installshield.

11

Thanks Vincent! I’ll install and test this build using a project I have in source control…no better backup than that! :slight_smile: I’ll keep you posted of my results!

Regards,
Tracey