Downloads:

5,366

Downloads of v 4.0.0.1313:

246

Last Update:

09 Sep 2019

Package Maintainer(s):

Software Author(s):

  • CodeValue LTD

Tags:

Debugging Extension vsix trial vs2017

OzCode Debugging extension for Visual Studio 2017

This is not the latest version of OzCode Debugging extension for Visual Studio 2017 available.

  • 1
  • 2
  • 3

4.0.0.1313 | Updated: 09 Sep 2019

Downloads:

5,366

Downloads of v 4.0.0.1313:

246

Maintainer(s):

Software Author(s):

  • CodeValue LTD

  • 1
  • 2
  • 3
OzCode Debugging extension for Visual Studio 2017 4.0.0.1313

This is not the latest version of OzCode Debugging extension for Visual Studio 2017 available.

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Exemption:

Requires Visual Studio to be installed.

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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

>

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

>

To uninstall OzCode Debugging extension for Visual Studio 2017, 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 https://community.chocolatey.org/api/v2/)


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 https://community.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. Copy Your Script

choco upgrade ozcode-vs2017 -y --source="'INTERNAL REPO URL'" --version="'4.0.0.1313'" [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-vs2017 -y --source="'INTERNAL REPO URL'" --version="'4.0.0.1313'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install ozcode-vs2017
  win_chocolatey:
    name: ozcode-vs2017
    version: '4.0.0.1313'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'ozcode-vs2017' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '4.0.0.1313'
end

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


cChocoPackageInstaller ozcode-vs2017
{
    Name     = "ozcode-vs2017"
    Version  = "4.0.0.1313"
    Source   = "INTERNAL REPO URL"
}

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


package { 'ozcode-vs2017':
  ensure   => '4.0.0.1313',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 09 Sep 2019.

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 2017. Use the OzCode package for Visual Studio 2012, 2013 and 2015.

The install script will install OzCode into all suitable instances of Visual Studio 2017.


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

$packageName  = 'ozcode-vs2017'
$toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$fileName     = 'OzCode_4.0.0.1313.vsix'
$checksum     = '61d7d831535b87945cabd4a4df371db8bec9b7d4da942af2e05c3ced40442fe0'
$fileFullPath = "$toolsDir\$fileName"

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

if (-not $runningAU) {
. $toolsDir\common.ps1
} else {
    # We don't want this file being put in the tools directory when running in AU
    $fileFullPath = "$ENV:Temp\$filename"
}


$packageArgs = @{
  packageName   = $packageName
  fileFullPath  = $fileFullPath
  url           = "http://downloads.oz-code.com/files/$fileName"  #download URL, HTTPS preferrred
  checksum      = $checksum
  checksumType  = 'sha256'
}

Get-ChocolateyWebFile @packageArgs

if (-not $runningAU) {
    & $vsixInstaller $fileFullPath /instanceIds:$vsInstances /logfile:`"$env:TEMP\$($packageName)\$($packageName).VsixInstall.log`" /quiet
}
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop';

$extensionId = "6c84f75d-38c3-48a2-9e54-d362238686b5"

. $toolsDir\common.ps1

# Be explicit about VS instances, otherwise uninstalling can affect older versions besides 2017
& $vsixInstaller /uninstall:$extensionId /instanceIds:$vsInstances /logfile:`"$env:TEMP\$($packageName)\$($packageName).VsixUninstall.log`" /quiet
tools\common.ps1
# Find latest VS 2017 instance
# We can't use Install-ChocolateyVsixPackage for 2017 yet.
$xml = [xml] (vswhere -version "[15.0,16.0)" -requires Microsoft.Net.ComponentGroup.DevelopmentPrerequisites -format xml)

if (-not $xml.instances.HasChildNodes) {
    Write-Error "No suitable instances of Visual Studio 2017 were found to install OzCode"
}

# Use highest version's VSIXInstaller
$vsixInstaller = (Join-Path $xml.instances.FirstChild.installationPath "Common7\IDE\VSIXInstaller.exe")

$vsInstances = $xml.instances.instance.instanceId -join ","

if (-not (Test-Path $vsixInstaller)) {
    Write-Error "Could not find VSIXInstaller.exe"
}

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
OzCode Debugging extension for Visual Studio 2017 and 2019 4.0.0.3513 234 Tuesday, November 3, 2020 Approved
OzCode Debugging extension for Visual Studio 2017 and 2019 4.0.0.3109 151 Monday, July 27, 2020 Approved
OzCode Debugging extension for Visual Studio 2017 and 2019 4.0.0.2842 151 Monday, June 1, 2020 Approved
OzCode Debugging extension for Visual Studio 2017 and 2019 4.0.0.2721 144 Friday, May 8, 2020 Approved
OzCode Debugging extension for Visual Studio 2017 and 2019 4.0.0.2637 127 Friday, April 24, 2020 Approved
OzCode Debugging extension for Visual Studio 2017 and 2019 4.0.0.2613 113 Wednesday, April 22, 2020 Approved
OzCode Debugging extension for Visual Studio 2017 and 2019 4.0.0.2540 145 Tuesday, April 7, 2020 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.2029 184 Tuesday, January 28, 2020 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.1632 231 Monday, November 11, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.1543 150 Thursday, October 24, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.1313 246 Monday, September 9, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.1229 197 Wednesday, August 7, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.983 224 Monday, July 1, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.822 197 Thursday, June 6, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.740 166 Saturday, May 18, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.658 205 Saturday, April 27, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.609 140 Monday, April 15, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.600 158 Friday, April 12, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 4.0.0.557 168 Monday, April 8, 2019 Approved
OzCode Debugging extension for Visual Studio 2017 3.1.0.3913 636 Thursday, June 8, 2017 Approved
OzCode Debugging extension for Visual Studio 2017 3.0.0.3893 356 Monday, May 29, 2017 Approved
OzCode Debugging extension for Visual Studio 2017 3.0.0.3887 408 Sunday, May 28, 2017 Approved
OzCode Debugging extension for Visual Studio 2017 3.0.0.3597 414 Sunday, May 21, 2017 Approved

Discussion for the OzCode Debugging extension for Visual Studio 2017 Package

Ground Rules:

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