• 1
  • 2
  • 3
Invantive Bridge for Developers 17.13.3-RC

This is a prerelease version of Invantive Bridge for Developers.

  • 1
  • 2
  • 3

Some Checks Are Exempted or Have Failed

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Exemption:

Reboot required due to dependencies.

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Invantive Bridge for Developers, run the following command from the command line or from PowerShell:

>

To upgrade Invantive Bridge for Developers, run the following command from the command line or from PowerShell:

>

To uninstall Invantive Bridge for Developers, 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 invantive-bridge-developers -y --source="'INTERNAL REPO URL'" --version="'17.13.3-RC'" --prerelease [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 invantive-bridge-developers -y --source="'INTERNAL REPO URL'" --version="'17.13.3-RC'" --prerelease
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install invantive-bridge-developers
  win_chocolatey:
    name: invantive-bridge-developers
    version: '17.13.3-RC'
    source: INTERNAL REPO URL
    state: present
    allow_prerelease: yes

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


chocolatey_package 'invantive-bridge-developers' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '17.13.3-RC'
  options  '--prerelease'
end

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


cChocoPackageInstaller invantive-bridge-developers
{
    Name        = "invantive-bridge-developers"
    Version     = "17.13.3-RC"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"
}

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


package { 'invantive-bridge-developers':
  ensure          => '17.13.3-RC',
  install_options => ['--prerelease'],
  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 is exempt from moderation. While it is likely safe for you, there is more risk involved.
Description

Invantive Bridge installation for use by Visual Studio Developers


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

$packageName= 'invantive-bridge-developers'

$packageArgs = @{
  packageName = $packageName
  fileType = 'MSI'
  url = 'https://download.invantive.com/release/msi/Invantive%20Bridge%20for%20Developers-17.13.3-RC.msi'
  url64bit = 'https://download.invantive.com/release/msi/Invantive%20Bridge%20for%20Developers-17.13.3-RC.msi'
  softwareName = 'Invantive Bridge for Developers'
  checksum = 'CBFD13CE8F953752FD5F720C57ADBDE265A3E633DE51EC7BADB7FDE3FFD0BD04'
  checksumType = 'sha256'
  checksum64 = 'CBFD13CE8F953752FD5F720C57ADBDE265A3E633DE51EC7BADB7FDE3FFD0BD04'
  checksumType64 = 'sha256'
  silentArgs = "/qn /norestart /l*v `"$env:Temp\invantive-bridge-developers-17.13.3-msi-install.log`""
  validExitCodes = @(0, 3010, 1641)
}

Install-ChocolateyPackage @packageArgs

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
Invantive Bridge for Developers 20.0.148 61 Friday, April 9, 2021 Approved
Invantive Bridge for Developers 20.0.145 51 Wednesday, March 3, 2021 Approved
Invantive Bridge for Developers 20.0.131 74 Tuesday, December 22, 2020 Approved
Invantive Bridge for Developers 17.32.33 325 Saturday, June 22, 2019 Approved
Invantive Bridge for Developers 17.28.0 155 Thursday, October 25, 2018 Approved
Invantive Bridge for Developers 17.24.9 209 Wednesday, July 11, 2018 Approved
Invantive Bridge for Developers 17.15.9-BETA 238 Friday, April 6, 2018 Approved
Invantive Bridge for Developers 17.15.8-BETA 218 Friday, April 6, 2018 Approved
Invantive Bridge for Developers 17.15.3-BETA 252 Friday, March 9, 2018 Approved

Included components:

  • Invantive.SQL.Windows 17.16.4-RC

Version 17.13.2-RC, released 2017-12-15:

  • Fix async method hanging on opening connection.

Version 17.12.3-RC, released 2017-12-11:

  • Circumvent bug in exception handling by Power BI releases up to at least 2017 Nov.
  • Adapt ADO.NET provider default language to Windows user interface language.
  • Determine data type for Invantive SQL based upon DbType provided for a DbParameter.

Version 17.11.12, released 2017-12-08:

  • Correct label of XML audit files to be match contents instead of always XML Auditfile Salaris 7.0.
  • Avoid error on Shared State not registered.
  • No longer actively create an IIID.
  • DDEX: Added provider information.

Discussion for the Invantive Bridge for Developers Package

Ground Rules:

  • This discussion is only about Invantive Bridge for Developers and the Invantive Bridge for Developers 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 Invantive Bridge for Developers, 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