Downloads of v


Last Update:

25 Jul 2018

Package Maintainer(s):

Software Author(s):

  • VSoft Technologies Pty. Ltd.


finalbuilder automation IDE build cmd CLI trial

FinalBuilder (Install)

This is not the latest version of FinalBuilder (Install) available.

  • 1
  • 2
  • 3 | Updated: 25 Jul 2018



Downloads of v



Software Author(s):

  • VSoft Technologies Pty. Ltd.

  • 1
  • 2
  • 3
FinalBuilder (Install)

This is not the latest version of FinalBuilder (Install) available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


Deployment Method: Individual Install, Upgrade, & Uninstall

To install FinalBuilder (Install), run the following command from the command line or from PowerShell:


To upgrade FinalBuilder (Install), run the following command from the command line or from PowerShell:


To uninstall FinalBuilder (Install), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade finalbuilder -y --source="'INTERNAL REPO URL'" --version="''" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade finalbuilder -y --source="'INTERNAL REPO URL'" --version="''" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install finalbuilder
    name: finalbuilder
    version: ''
    state: present

See docs at

chocolatey_package 'finalbuilder' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller finalbuilder
    Name     = "finalbuilder"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'finalbuilder':
  ensure   => '',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 22 Feb 2019.


FinalBuilder provides a graphical IDE and command line to create, debug, and run software build projects. FinalBuilder includes many actions to perform tasks at all stages of the continuous software delivery cycle.

The package will download and install FinalBuilder with the default settings. Obtaining a 30 day trail license for each new installation is required. After the trial period a full licence is required from our [store] (

Built In Actions

Over 700 actions are included for common software delivery tasks. Notiable groups of these actions include;

  • Build logic - If..Then, Try..Catch..Finally, Switch, While, Iterator, and Async
  • Version control - AccuRev, CVS, Git, ClearCase, JediVCS, Mercurial, TFS, Plastic SCM, PureCM, Perforce, QVCS, Subversion, Surround, and Sourcegear Vault
  • Compilers - Visual Studio .Net, Delphi, Java, and Visual Basic
  • Build - Ant, NAnt, MSBuild, and Maven
  • Testing - NUnit, MbUnit, MSTest\VSTest, TestComplete, AQTest, and Typemock
  • Installer - InnoSetup, InstallAware, Wise, InstallAnywhere, GP Install, NullSoft, InstallShield, Advanced Installer, Setup Factory, Wix, and MSI
  • Deployment - Web Deploy, EC2, IIS, FTP, and SFTP
  • Configuration - .Net, HyperV, VWWare, XML, Windows OS, and IIS

Custom Scripting

All actions provide customisation through settings as well as scripting events. These events allow custom scripted behaviour to be performed. Supported languages for scripts are JScript, VBScript, PowerShell, and IronPython.

Custom Actions - Action Studio

Custom actions are used for large or complex custom scripting requirements. These custom actions can be backed by scripting logic or C# implementations. Custom action styles that can be written include;

  • Standard Actions - Simple actions that don't call an external tool.
  • Execute Actions - Actions that call an external tool to perform the desired task.
  • Iterator Actions - Tasks that require their repetition to be simplified in builds.

$ErrorActionPreference = 'Stop'; #Stop on all errors

$packageName = 'finalbuilder' #Unique name of the package
$installerType = 'EXE' #Installer is an executable.
$url = '' #URL to download installer for current version. 
$silentArgs = '/SP /VERYSILENT /SUPPRESSMSGBOXES /CLOSEAPPLICATIONS' #Silent install arguments for our installer
$validExitCodes = @(0) #Valid return codes from the installer for success
$checksum = 'A170D888572E6B3DD5F28BB10AB10E422D9E013470627C69F8F5E631BA67EEF4'

#Run chocolatey install package commandlet
Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" "$url" -validExitCodes $validExitCodes -checksum $checksum -checksumType sha256
$ErrorActionPreference = 'Stop'; #Stop on all errors

$packageName = 'finalbuilder' #Unique name of the package
$registryUninstallerKeyName = '{62D2B81F-145D-4926-A198-449B18290ABD}_is1' #The uninstall registry key for our application. Defined and setup by the installer exe.
$installerType = 'EXE' #Our uninstaller is also an executable
$silentArgs = '/SILENT /VERYSILENT /SUPPRESSMSGBOXES' #Silent arguments to make the uninstaller not show any GUI
$validExitCodes = @(0) #Valid return codes from the uninstaller for success

$shouldUninstall = $true; #We should uninstall if we detect no errors. 
#Keys where our uninstall data is stored in registry
$local_key       = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$local_key6432   = "HKCU:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$machine_key     = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$machine_key6432 = "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"

#Try each key. The first to return a valid path, and key get the UninstallString value from it. 
$file = @($local_key, $local_key6432, $machine_key, $machine_key6432) `
    | ?{ Test-Path $_ } `
    | Get-ItemProperty `
    | Select-Object -ExpandProperty UninstallString

#If we don't have a valid uninstall executable, then error and don't run uninstall. 
if ($file -eq $null -or $file -eq '') {
    Write-Host "$packageName has already been uninstalled by other means."
    $shouldUninstall = $false
#If we are still uninstalling then call chocolatey uninstall package commandlet to run our uninstaller
if ($shouldUninstall) {
 Uninstall-ChocolateyPackage -PackageName $packageName -FileType $installerType -SilentArgs "$silentArgs" -validExitCodes $validExitCodes -File "$file"

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
FinalBuilder (Install) 55 Monday, October 18, 2021 Approved
FinalBuilder (Install) 56 Thursday, September 9, 2021 Approved
FinalBuilder (Install) 14 Thursday, September 9, 2021 Approved
FinalBuilder (Install) 74 Monday, July 5, 2021 Approved
FinalBuilder (Install) 86 Monday, April 12, 2021 Approved
FinalBuilder (Install) 72 Friday, January 29, 2021 Approved
FinalBuilder (Install) 71 Monday, December 7, 2020 Approved
FinalBuilder (Install) 56 Wednesday, November 4, 2020 Approved
FinalBuilder (Install) 80 Wednesday, September 30, 2020 Approved

Release notes are located at FinalBuilder Version History

This package has no dependencies.

Discussion for the FinalBuilder (Install) Package

Ground Rules:

  • This discussion is only about FinalBuilder (Install) and the FinalBuilder (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or FinalBuilder (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus