# Wise Installation Studio 7.0 bug
**URL:** https://www.finalbuilder.com/forums/t/wise-installation-studio-7-0-bug/3228
**Category:** Bugs
**Created:** [March 24, 2010, 3:22am UTC](https://www.finalbuilder.com/forums/t/wise-installation-studio-7-0-bug/3228 "2010-03-24T03:22:39Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [March 24, 2010, 3:22am UTC](https://www.finalbuilder.com/forums/t/wise-installation-studio-7-0-bug/3228/1 "2010-03-24T03:22:39Z")
The Wise Wiindows Installer action triggers a bug in Wise Installation Studio 7.0.
The file versions for the files included with the install project are not updated in the resulting msi. And if I remember correctly there where also some other failures.
This is not exactly a bug in FinalBuilder, but the action is useless, as it can not build a correct install package with Wise Installation Studio 7.0.
More about the problem here:
[https://kb.altiris.com/display/1/kb...n=13&s](https://kb.altiris.com/display/1/kb/article.asp?aid=36476&n=13&s)=
The problem can be worked around, if you change the action implementation to use OLE automation, instead of command line execution.
I use the following script now, to build my install packages:
//////////////////////////////////////
//setup
ActionResult = false; //default result
var strProjectFile = FBVariables.PROJECT\_BUILD\_PATH+'\\someproject.wsi';
var strProjectVersion = FBVariables.PROJECT\_VERINFO\_PRODUCT\_VERSIONNUMBER;
var strProjectName = ProductVersionInfo.ProductName;
var strProductMfg = ProductVersionInfo.CompanyName;
//var strReleaseToBuild = 'Default';
//////////////////////////////////////
//run
Action.SendLogMessage('Creating Wise for Windows Installer object');
var wiseProject = new ActiveXObject('WFWI.WFWIProject');
wiseProject.SilentMode = true;
wiseProject.ThrowExceptions = true;
Action.SendLogMessage('Opening project file: '+strProjectFile);
wiseProject.Open(strProjectFile);
wiseProject.Version = strProjectVersion;
wiseProject.Manufacturer = strProductMfg;
wiseProject.ProductName = strProjectName;
Action.SendLogMessage(' ProductName: '+wiseProject.ProductName);
Action.SendLogMessage(' Manufacturer: '+wiseProject.Manufacturer);
Action.SendLogMessage(' Version: '+wiseProject.Version);
wiseProject.Properties.Item('ProductCode').Value = wiseProject.GenerateGuid();
Action.SendLogMessage('Saving project file: '+strProjectFile);
wiseProject.Save(strProjectFile);
FBVariables.PROJECT\_CLIENT\_MsiProductCode = wiseProject.ProductCode;
Action.SendLogMessage('ProductCode: '+wiseProject.ProductCode+' '
+FBVariables.PROJECT\_CLIENT\_MsiProductCode);
Action.SendLogMessage('Compiling project file: '+strProjectFile);
var compileResult;
compileResult = wiseProject.Compile(strProjectFile);
wiseProject = null;
if (compileResult) {
Action.SendLogMessage('SUCCESS');
ActionResult = true;
} else {
Action.SendLogMessage('FAILURE');
ActionResult = false;
//throw 'Failed to compile Wise for Windows Installer project.';
}
---
### Author:  [@paulsamways](https://www.finalbuilder.com/forums/u/paulsamways)
#### Post date: [March 24, 2010, 11:23am UTC](https://www.finalbuilder.com/forums/t/wise-installation-studio-7-0-bug/3228/2 "2010-03-24T11:23:36Z")
Hi Christoph,
Thanks for explaining the bug and offering a workaround for this bug with Wise Installation Studio 7.0. Has Symantec released any information about whether this bug will be fixed?
Regards,
Paul.
---
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [April 8, 2010, 1:23am UTC](https://www.finalbuilder.com/forums/t/wise-installation-studio-7-0-bug/3228/3 "2010-04-08T01:23:13Z")
I have not found anything about Symantec wanting to fix anything regarding Wise Installation Studio.
-rant-
As I see it, Symantec has no interrest in the product, they only have it because it was included when they bought Altiris, and the product will die. This is IMHO typical Symantec, I have had similar experiences with other "now Symantec" products. As soon as a product gets infected with the Symantec brand, you can flush it.
-rant-
We will use other tools (wix or i don't know yet) for new windows installer projects, and eventually also migrate our existing Wise Installation Studio projects over. But for now we have to keep the Wise Installation Studio projects building.
I can understand if you do not want to bother spending time and money on getting that symantec piece of crap working in FinalBuilder, but maybe you could add some info about the workaround to the help file (or action description) for other poor souls to find.