Downloads:

1,624

Downloads of v 2.12.4.744:

921

Last Update:

03 Jan 2015

Package Maintainer(s):

Software Author(s):

  • Alexej Hirsch

Tags:

bugShooting bug shooting screenCapture capture screen

Bug Shooting

2.12.4.744 | Updated: 03 Jan 2015

Downloads:

1,624

Downloads of v 2.12.4.744:

921

Maintainer(s):

Software Author(s):

  • Alexej Hirsch

Tags:

bugShooting bug shooting screenCapture capture screen

Bug Shooting 2.12.4.744

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Failing Test

Hide Checks
Hide Checks

Validation Testing Unknown

Verification Testing Failed

Details

To install Bug Shooting, run the following command from the command line or from PowerShell:

>

To upgrade Bug Shooting, run the following command from the command line or from PowerShell:

>

To uninstall Bug Shooting, 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 bugshooting -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 bugshooting -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 bugshooting installed
  win_chocolatey:
    name: bugshooting
    state: present
    version: 2.12.4.744
    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 'bugshooting' do
  action    :install
  version  '2.12.4.744'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: bugshooting,
    Version: 2.12.4.744,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller bugshooting
{
   Name     = 'bugshooting'
   Ensure   = 'Present'
   Version  = '2.12.4.744'
   Source   = 'STEP 3 URL'
}

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


package { 'bugshooting':
  provider => 'chocolatey',
  ensure   => '2.12.4.744',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install bugshooting version="2.12.4.744" 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 approved by moderator ferventcoder on 03 Feb 2015.

Description

With Bug Shooting, creating screen captures and sending them to various bug tracking and issue management systems, e-mail, image editing and instant messaging applications is done in a breeze.

Intelligent capture mode

  • With the intelligent capture mode, it is as simple as never before to capture the screen. You can capture an area, a window, or the full screen, without having to change the capture mode. Try it out, you will love it.
  • Magnifier supports you during the capture and allow pixel-fine region selection.

Edit functions

  • Create professional graphics by adding different effects to your screenshots. Add text, arrows or other graphics.
  • The tool gallery gives you easy and quick access to frequently used tools. The gallery may be adapted to your needs.
  • Screenshots sometimes contain secret information (e.g. passwords) that should not be passed on. With the blur tool you can hide such information by blurring them so they cannot be recognized.

Share screenshots

  • Send your Screenshots directly to different applications (Outputs). Bug Shooting supports many Outputs, such as bug tracking and issue management systems, e-mail, image editing and instant messaging applications. Following applications are supported:
    FogBugz, Gemini, OnTime, BugTracker.NET, Mantis BT, Done.Done., JIRA, Bugzilla, SpiraTest, elementool, Unfuddle, informUp, BugNET, BUGtrack, YouTRACK, Assembla, ImageShack, Twitpic, Abload.de, Skype, Lync 2010, Default Email Client, Gimp, MS Outlook, MS Word, MS Excel, MS Paint, Thunderbird, FTP, Command line
  • Of course, you can save your graphics in various image file format and print them as well.

Other functions

  • Bug Shooting automatically storage the captured screenshots and the edited graphics in a library. This provides you with quick access to your captures.
  • Bug Shooting provide functions for direct storage of screenshots on the hard drive or for sending these to an Output without editing the screenshot in the editor.
  • Bug Shooting provides an API (Application Programming Interface ) for creation of custom Outputs. See the documentation of the Output API here.

Free for personal use

bugShooting-logo.png
tools\chocolateyInstall.ps1 
# Package requires .net 3.5

$osInfo = Get-WmiObject Win32_OperatingSystem | select-object Version
$osInfo.Version = [version] $osInfo.Version

if ($osInfo.Version -lt [version]'6.2') 
{
    # Less than 2012/Win8, test if the directory is present for .net3.5
    if( !(test-path 'C:\WINDOWS\Microsoft.NET\Framework\v3.5') )
    {
        choco install DotNet3.5
    }
}

else 
{
    $check35 = get-WindowsFeature Net-Framework-Core
    if( $check35.installed -eq $False)
    {
        install-windowsFeature Net-Framework-Core
    }
}

# End of .Net 3.5 install hackery... smh

$packageName = 'bugshooting'
$fileType = 'exe'
$url = 'http://www.bugshooting.com/Home/Download?Mode=Start'
$silentArgs = "/SILENT /LINKDESKTOP=0 /MULTIUSER=1 /LINKAUTOSTART=1"

install-ChocolateyPackage -packageName $packageName -fileType $fileType -silentArgs $silentArgs -url $url

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
Bug Shooting 2.12.4.744 921 Saturday, January 3, 2015 Approved
Bug Shooting 2.12.2.731 703 Tuesday, January 21, 2014 Unknown

This package has no dependencies.

Discussion for the Bug Shooting Package

Ground Rules:

  • This discussion is only about Bug Shooting and the Bug Shooting 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 Bug Shooting, 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