I just downloaded the community download "Installer...blabla". I copied the the *.fbapx into the ActionDefs and started FB. I started to use the action type and got allways a validation script error in line 171, char 102 - something like "not closed constant".
After some clicking around to get this problem away I got a crash. Because it happens on the build machine I cannot send an problem report per email.
Sorry to hear you’re having problems. The “*.fbapx” this case was “FBInstallers.fbap”, right? I just installed this on FinalBuilder 5.5.240, and it seems to validate just fine on my machine.
Did you install anything else at the same time? If you open FBInstallers.fbap in ActionStudio, does it open and save correctly or are there errors reported?
> “FBInstallers.fbap”, right? no, it was the FBInstallers.fbapx. I copied it from the FBInstaller.zip to the ActionDef directory. It seems, that I can use all action from the Install Builders action without any trouble but if I use the “InstallShield change MSI propterties” action a “Validation Errors” occurs: Line 171, Char 102 - Package Common Script - OnValidate - Something like “Not closed String”. Can it be a problem with the german directory environment?
I think that, by mistake, two different packages were submitted to the Community Downloads.
The one that you have is an old one, we’ll delete it from the community downloads.
The one that you want is labelled “Various actions for manipulating MSI, Wise, and In”. If you click on “Community Downloads”, click Categories->FinalBuilder, and Sort By->Date, then you should be the first package listed. Delete the .FBInstallers.fbapx file, and copy the .fbap file instead.
Sorry for the confusion. Please let us know how you go.
I am now using a small pre action script for my problem. That is working fine.
If I could have a wish: Please improve your samples/help.
> The one that you want is labelled “Various actions for manipulating MSI, Wise, and In”. If you click on “Community Downloads”, click Categories->FinalBuilder, and Sort By->Date, then you should be the first package listed. Delete the .FBInstallers.fbapx file, and copy the .fbap file instead.
I copied the FBInstaller.fbap and the validation script error vanished.
> The one that you have is an old one, we’ll delete it from the community downloads. They are both still in the community downloads: InstallShield and WISE MSI Updater Actions - Raoul Molenkamp Various actions for manipulating MSI, Wise, and In - Tate Needham
I’m glad it’s all working. The situation with the community downloads packages is that the broken “Tate Needham” package, despite being newer, is actually an old version. I’ve contacted Raoul, who is the author of the package, and asked him to fix the bug in the newer version. The “Tate Needham” package has been deleted.
If Tate’s version is working fine for you, though, then by all means keep using it.
(Sorry, that’s very confusing!)
>If I could have a wish: Please improve your samples/help.
Is there anything in particular you’d like more help/samples for? In the case of the “Community Downloads” packages, they are user-contributed so there is a limited amount of work we can do to support them.
>Is there anything in particular you’d like more help/samples for? In the case of the “Community Downloads” packages, they are user-contributed so there is a limited amount of work we can do to support them.
My biggest problem is/was always not to know where to look. For lot of small things I spend hours in the documentation. I would love to have an example for a complete build process. Even if it is only to see what is good/supported/possible style when using FinalBuilder. The example should start with some directory preperations, then getting files from “SourceControl”, after that doing some cool (script) stuff on the files, now building three time “hello world” in version 2.0.1.300, put it all together in a setup and finally place it somewhere on the computer. Everything mixed up with some “IF/ELSE”, “TRY/CATCH”, “LOOP/ITERATOR” and Before and After Actions as highlight. It mustnot be simple, it must give an overview.
> If Tate’s version is working fine for you, though, then by all means keep using it.
I think, I am using Raouls version at the moment… but it does not matter any more ;-).