Downloads:

2,511

Downloads of v 1.0.2:

360

Last Update:

12/18/2012

Package Maintainer(s):

Software Author(s):

  • John Batte

Tags:

batte utilities tools chocolatey

Batte.LoadOuts.Dev

This is not the latest version of Batte.LoadOuts.Dev available.

1.0.2 | Updated: 12/18/2012

Downloads:

2,511

Downloads of v 1.0.2:

360

Maintainer(s):

Software Author(s):

  • John Batte

Batte.LoadOuts.Dev 1.0.2

This is not the latest version of Batte.LoadOuts.Dev available.

All Checks are Unknown

2 Test of Unknown Status


Validation Testing Unknown


Verification Testing Unknown

To install Batte.LoadOuts.Dev, run the following command from the command line or from PowerShell:

>

To upgrade Batte.LoadOuts.Dev, run the following command from the command line or from PowerShell:

>

To uninstall Batte.LoadOuts.Dev, 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 https://chocolatey.org/api/v2. 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 https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade batte.loadouts.dev -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 batte.loadouts.dev -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure batte.loadouts.dev installed
  win_chocolatey:
    name: batte.loadouts.dev
    state: present
    version: 1.0.2
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'batte.loadouts.dev' do
  action    :install
  version  '1.0.2'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: batte.loadouts.dev,
    Version: 1.0.2,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller batte.loadouts.dev
{
   Name     = 'batte.loadouts.dev'
   Ensure   = 'Present'
   Version  = '1.0.2'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'batte.loadouts.dev':
  provider => 'chocolatey',
  ensure   => '1.0.2',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install batte.loadouts.dev version="1.0.2" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.

Description

Batte.LoadOuts.Dev is a .NET developer workstation loadout, including Visual Studio 2012 Professional, ReSharper 7, and more.


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
Batte.LoadOuts.Dev 1.0.4 287 Tuesday, December 18, 2012 Unknown
Batte.LoadOuts.Dev 1.0.3 340 Tuesday, December 18, 2012 Unknown
Batte.LoadOuts.Dev 1.0.2 360 Tuesday, December 18, 2012 Unknown
Batte.LoadOuts.Dev 1.0.1 295 Tuesday, December 18, 2012 Unknown
Batte.LoadOuts.Dev 1.0.0 328 Tuesday, November 20, 2012 Unknown
Discussion for the Batte.LoadOuts.Dev Package

Ground Rules:

  • This discussion is only about Batte.LoadOuts.Dev and the Batte.LoadOuts.Dev 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 Batte.LoadOuts.Dev, 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