Downloads of v 1.00:


Last Update:

17 Mar 2015

Package Maintainer(s):

Software Author(s):

  • Paul Kulchenko
  • ZeroBrane® LLC



Zerobrane Studio (Install)

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

1.00 | Updated: 17 Mar 2015



Downloads of v 1.00:



Software Author(s):

  • Paul Kulchenko
  • ZeroBrane® LLC



Zerobrane Studio (Install) 1.00

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

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Passing Test

Validation Testing Unknown

Verification Testing Passed


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


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


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


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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade zerobrane-studio.install -y --source="'STEP 3 URL'" [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 zerobrane-studio.install -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure zerobrane-studio.install installed
    name: zerobrane-studio.install
    state: present
    version: 1.00
    source: STEP 3 URL

See docs at

chocolatey_package 'zerobrane-studio.install' do
  action    :install
  version  '1.00'
  source   'STEP 3 URL'

See docs at

    Name: zerobrane-studio.install,
    Version: 1.00,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller zerobrane-studio.install
   Name     = 'zerobrane-studio.install'
   Ensure   = 'Present'
   Version  = '1.00'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'zerobrane-studio.install':
  provider => 'chocolatey',
  ensure   => '1.00',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install zerobrane-studio.install version="1.00" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved by moderator ferventcoder on 24 May 2015.


ZeroBrane Studio is a lightweight Lua IDE with code completion, syntax highlighting, live coding, code analyzer, and debugging support for Lua 5.1, Lua 5.2, Lua 5.3, LuaJIT, and other Lua engines.


Currently (1.00) Zerobrane provides a portable .zip
and an "installer" .exe which is really a self-extracting zip
that also adds a shortcut to the Start Menu.
It doesn't have a default "install" location, nor does it get listed
in Add/Remove Programs.

In order to prevent confusion (and allow for changes in future)
I have provided two packages which closely mimic the two options
for acquiring Zerobrane on Windows.

However, in the name of safety I use the .zip for both
(I don't know if Install-ChocolateyZipPackage works with .exes)

So the .install package only differs in that it adds a shortcut :)

$name = 'zerobrane-studio.install'
$url = ''
$installPath = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

Install-ChocolateyZipPackage $name $url $installPath

# For some unknown reason, this Lua file is read-only by default
# which really screws with uninstallation!
# So we'll do something about it.
attrib -r (join-path $installPath "myprograms/testwell.lua")

# Place Start Menu Shortcut (mimicking Zerobrane's own self-extracting .exe)
$shortcutPath = join-path $env:appdata "Microsoft\Windows\Start Menu\Programs"
$shortcutName = "ZeroBrane Studio Lua IDE"
$lnkPath = join-path $shortcutPath ($shortcutName + ".lnk")
$targetPath = join-path $installPath "zbstudio.exe"

Install-ChocolateyShortcut -shortcutFilePath $lnkPath -targetPath $targetPath -description $shortcutName
$packageName = 'zerobrane-studio.install'
$zipFileName = ''

# UnInstall-ChocolateyZipPackage doesn't work as expected in 0.9.9
# So we'll do it manually!

# UnInstall-ChocolateyZipPackage $packageName $zipFileName
try {
    remove-item $packageLibPath -recurse
	# Also remove the shortcut we added
	$shortcutPath = join-path $env:appdata "Microsoft\Windows\Start Menu\Programs"
	$shortcutName = "ZeroBrane Studio Lua IDE"
	$lnkPath = join-path $shortcutPath ($shortcutName + ".lnk")
	remove-item $lnkPath
} catch {
	throw $_.Exception

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.

Version Downloads Last Updated Status
Zerobrane Studio (Install) 1.80 417 Sunday, December 23, 2018 Approved
Zerobrane Studio (Install) 709 Tuesday, October 13, 2015 Approved
Zerobrane Studio (Install) 277 Monday, July 13, 2015 Approved
Zerobrane Studio (Install) 1.00 332 Tuesday, March 17, 2015 Approved

This package has no dependencies.

Discussion for the Zerobrane Studio (Install) Package

Ground Rules:

  • This discussion is only about Zerobrane Studio (Install) and the Zerobrane Studio (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 Zerobrane Studio (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