Downloads:
2,462
Downloads of v 3.0.0.3893:
427
Last Update:
29 May 2017
Package Maintainer(s):
Software Author(s):
- CodeValue LTD
Tags:
debugging extension admin vsix trialOzCode Debugging extension for Visual Studio
- 1
- 2
- 3
3.0.0.3893 | Updated: 29 May 2017
Downloads:
2,462
Downloads of v 3.0.0.3893:
427
Maintainer(s):
Software Author(s):
- CodeValue LTD
OzCode Debugging extension for Visual Studio 3.0.0.3893
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by CodeValue LTD. The inclusion of CodeValue LTD trademark(s), if any, upon this webpage is solely to identify CodeValue LTD goods or services and not for commercial purposes.
- 1
- 2
- 3
This Package Contains an Exempted Check
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
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:
Deployment Method:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download ozcode --internalize --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade ozcode -y --source="'INTERNAL REPO 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="'INTERNAL REPO URL'"
$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
win_chocolatey:
name: ozcode
version: '3.0.0.3893'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'ozcode' do
action :install
source 'INTERNAL REPO URL'
version '3.0.0.3893'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller ozcode
{
Name = "ozcode"
Version = "3.0.0.3893"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'ozcode':
ensure => '3.0.0.3893',
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 by moderator Pauby on 01 Jun 2017.
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.
## NOTE: In 80-90% of the cases (95% with licensed versions due to Package Synchronizer and other enhancements),
## AutoUninstaller should be able to detect and handle registry uninstalls
## See https://chocolatey.org/docs/commands-uninstall
## and https://chocolatey.org/docs/helpers-uninstall-chocolatey-package
$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
#OTHERS
# Uncomment matching EXE type (sorted by most to least common)
#silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART' # Inno Setup
#silentArgs = '/s' # InstallShield
#silentArgs = '/s /v"/qn"' # InstallShield with MSI
#silentArgs = '/s' # Wise InstallMaster
#silentArgs = '-s' # Squirrel
#silentArgs = '-q' # Install4j
#silentArgs = '-s -u' # Ghost
# Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence.
#silentArgs = '' # none; make silent with input macro script like AutoHotKey (AHK)
# https://chocolatey.org/packages/autohotkey.portable
validExitCodes= @(0)
}
$uninstalled = $false
# Get-UninstallRegistryKey is new to 0.9.10, if supporting 0.9.9.x and below,
# take a dependency on "chocolatey-uninstall.extension" in your nuspec file.
# This is only a fuzzy search if softwareName includes '*'. Otherwise it is
# exact. In the case of versions in key names, we recommend removing the version
# and using '*'.
[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"}
}
## OTHER HELPERS
## https://chocolatey.org/docs/helpers-reference
#Uninstall-ChocolateyZipPackage @packageArgs # Only necessary if you did not unpack to package directory - see https://chocolatey.org/docs/helpers-uninstall-chocolatey-zip-package
#Uninstall-ChocolateyEnvironmentVariable # 0.9.10+ - https://chocolatey.org/docs/helpers-uninstall-chocolatey-environment-variable
#Uninstall-BinFile # Only needed if you used Install-BinFile - see https://chocolatey.org/docs/helpers-uninstall-bin-file
## Remove any shortcuts you added
; 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.
- ozcode.3.0.0.3893.nupkg (214530aad702) - ## / 58
- OzCode_3.0.0.3893.exe (7249952b9dbf) - ## / 61
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 3.0.0.3893 | 427 | Monday, May 29, 2017 | Approved | |
OzCode Debugging extension for Visual Studio 3.0.0.3887 | 456 | Sunday, May 28, 2017 | Approved | |
OzCode Debugging extension for Visual Studio 3.0.0.3597 | 383 | Wednesday, May 24, 2017 | Approved | |
OzCode Debugging extension for Visual Studio 2.0.0.1029 | 355 | Tuesday, May 23, 2017 | Approved |
2017 CodeValue LTD
-
- autohotkey.portable (≥ 1.1.25)
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.