Downloads:

1,660

Downloads of v 3.1.0.3913:

659

Last Update:

08 Jun 2017

Package Maintainer(s):

Software Author(s):

  • CodeValue LTD

Tags:

Debugging Extension admin vsix trial

OzCode Debugging extension for Visual Studio

3.1.0.3913 | Updated: 08 Jun 2017

Downloads:

1,660

Downloads of v 3.1.0.3913:

659

Maintainer(s):

Software Author(s):

  • CodeValue LTD

Tags:

Debugging Extension admin vsix trial

OzCode Debugging extension for Visual Studio 3.1.0.3913

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test

Hide Checks
Hide Checks

Validation Testing Passed

Verification Testing Exempt:

Requires Visual Studio to be installed

To install OzCode Debugging extension for Visual Studio, run the following command from the command line or from PowerShell:

>

To upgrade OzCode Debugging extension for Visual Studio, run the following command from the command line or from PowerShell:

>

To uninstall OzCode Debugging extension for Visual Studio, 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 ozcode -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 ozcode -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 ozcode installed
  win_chocolatey:
    name: ozcode
    state: present
    version: 3.1.0.3913
    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 'ozcode' do
  action    :install
  version  '3.1.0.3913'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: ozcode,
    Version: 3.1.0.3913,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller ozcode
{
   Name     = 'ozcode'
   Ensure   = 'Present'
   Version  = '3.1.0.3913'
   Source   = 'STEP 3 URL'
}

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


package { 'ozcode':
  provider => 'chocolatey',
  ensure   => '3.1.0.3913',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install ozcode version="3.1.0.3913" 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.

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

This package was approved by moderator gep13 on 08 Jun 2017.

Description

Debug like a magician.

Cut debugging time in half with the legendary Visual Studio extension for C#

Features include:

  • Linq Debugging
  • Export
  • Head-Up Display
  • Breakpoints
  • Exceptions
  • Trace
  • Quick Attach
  • Search
  • Foresee
  • Compare
  • Reveal
  • Custom Expressions
  • Filter Collections
  • Quick Actions
  • Show All Instances

Supported versions

This package supports Visual Studio 2012, 2013 and 2015. Use the OzCode-vs2017 package for Visual Studio 2017.

tools\chocolateyinstall.ps1 
$ErrorActionPreference = 'Stop';

$packageName  = 'ozcode'
$toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$download_dir = "$Env:TEMP\chocolatey\$packageName\$Env:ChocolateyPackageVersion".Replace("chocolatey\chocolatey", "chocolatey")
$fileLocation = ''
$filename = 'OzCode_3.1.0.3913.exe'
$checksum = 'b9ec99e041d65ed4dd44a1bf9d3fa09bb3561936dc1add90e55403afdb86c4f9'

# Flag whether we're being invoked by AU module
[bool] $runningAU = (Test-Path Function:\au_GetLatest)

if (-not (Test-Path $download_dir)) {
    New-Item -ItemType Directory $download_dir #| Out-Null
}

$packageArgs = @{
  packageName   = $packageName
  softwareName  = 'ozcode*'
  fileType      = 'exe'
  fileFullPath = "$download_dir\$fileName"
  silentArgs    = "" # NSIS  
  validExitCodes= @(0)
  url           = "http://downloads.oz-code.com/files/$filename"
  checksum      = $checksum
  checksumType  = 'sha256'
}

Get-ChocolateyWebFile @packageArgs

if (-not $runningAU) {
    Start-Process 'AutoHotkey' "$toolsDir\install.ahk"

    Install-ChocolateyInstallPackage @packageArgs 
}
tools\chocolateyuninstall.ps1 
$ErrorActionPreference = 'Stop';

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'ozcode*'  #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
  fileType      = 'exe'
  silentArgs    = "/S" # NSIS

  validExitCodes= @(0)
}

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey @packageArgs

if ($key.Count -eq 1) {
  $key | % { 
    $packageArgs['file'] = "$($_.UninstallString)"
    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
      $packageArgs['file'] = ''
    }

    Uninstall-ChocolateyPackage @packageArgs
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$env:ChocolateyPackageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}
}
tools\install.ahk 
; License agreement
SetKeyDelay, 10, 10

WinWait, OzCode Setup, License Agreement
IfNotEqual, ErrorLevel, 0, exit 1

ControlSend,, !a, OzCode Setup

WinWait, OzCode Setup, integration
IfNotEqual, ErrorLevel, 0, exit 1

ControlGet, NextEnabled, Enabled, ,Button2, OzCode Setup ; Check if Next button enabled

If NextEnabled = 0
{
	ControlSend,, {Esc}, OzCode Setup
	
	WinWait, OzCode Setup, Are you sure, 20
	
	ControlSend,, !y, OzCode Setup, Are you sure
	exit 2
}

ControlSend,, !n, OzCode Setup

WinWait, OzCode Setup, Prerequirements, 20
IfNotEqual, ErrorLevel, 0, exit 1

ControlSend,, !n, OzCode Setup
WinWait, OzCode Setup, successfully,20
IfNotEqual, ErrorLevel, 0, exit 1

ControlSend,, !f, OzCode Setup

WinWaitClose ; wait for dialog to close

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
OzCode Debugging extension for Visual Studio 3.1.0.3913 659 Thursday, June 8, 2017 Approved
OzCode Debugging extension for Visual Studio 3.0.0.3893 228 Monday, May 29, 2017 Approved
OzCode Debugging extension for Visual Studio 3.0.0.3887 303 Sunday, May 28, 2017 Approved
OzCode Debugging extension for Visual Studio 3.0.0.3597 230 Wednesday, May 24, 2017 Approved
OzCode Debugging extension for Visual Studio 2.0.0.1029 240 Tuesday, May 23, 2017 Approved
Discussion for the OzCode Debugging extension for Visual Studio Package

Ground Rules:

  • This discussion is only about OzCode Debugging extension for Visual Studio and the OzCode Debugging extension for Visual Studio 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 OzCode Debugging extension for Visual Studio, 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