Invantive Bridge for Developers 17.14.6-BETA

This is a prerelease version of Invantive Bridge for Developers.

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

Reboot required due to dependencies.

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:

>

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 invantive-bridge-developers -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 invantive-bridge-developers -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 invantive-bridge-developers installed
  win_chocolatey:
    name: invantive-bridge-developers
    state: present
    version: 17.14.6-BETA
    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 'invantive-bridge-developers' do
  action    :install
  version  '17.14.6-BETA'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: invantive-bridge-developers,
    Version: 17.14.6-BETA,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller invantive-bridge-developers
{
   Name     = 'invantive-bridge-developers'
   Ensure   = 'Present'
   Version  = '17.14.6-BETA'
   Source   = 'STEP 3 URL'
}

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


package { 'invantive-bridge-developers':
  provider => 'chocolatey',
  ensure   => '17.14.6-BETA',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install invantive-bridge-developers version="17.14.6-BETA" 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 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.14.6-BETA.msi'
  url64bit = 'https://download.invantive.com/release/msi/Invantive%20Bridge%20for%20Developers-17.14.6-BETA.msi'
  softwareName = 'Invantive Bridge for Developers'
  checksum = '8ACCB5AF205849913841F4832DF43C5723255043C3CB97F84650B0EBC0015C0B'
  checksumType = 'sha256'
  checksum64 = '8ACCB5AF205849913841F4832DF43C5723255043C3CB97F84650B0EBC0015C0B'
  checksumType64 = 'sha256'
  silentArgs = "/qn /norestart /l*v `"$env:Temp\invantive-bridge-developers-17.14.6-msi-install.log`""
  validExitCodes = @(0, 3010, 1641)
}

Install-ChocolateyPackage @packageArgs

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
Invantive Bridge for Developers 17.28.0 79 Thursday, October 25, 2018 Approved
Invantive Bridge for Developers 17.24.9 115 Wednesday, July 11, 2018 Approved
Invantive Bridge for Developers 17.15.9-BETA 139 Friday, April 6, 2018 Approved
Invantive Bridge for Developers 17.15.8-BETA 128 Friday, April 6, 2018 Approved
Invantive Bridge for Developers 17.15.3-BETA 154 Friday, March 9, 2018 Approved
Invantive Bridge for Developers 17.15.0 151 Tuesday, March 6, 2018 Approved
Invantive Bridge for Developers 17.14.12-BETA 140 Thursday, February 22, 2018 Exempted
Invantive Bridge for Developers 17.14.7-BETA 160 Wednesday, February 14, 2018 Exempted
Invantive Bridge for Developers 17.14.6-BETA 164 Thursday, December 28, 2017 Exempted

Included components:

  • Invantive.SQL.Windows 17.19.4-BETA

Version 17.14.5-BETA, released 2017-12-22:

  • Enable configuration of license through environment variable or fixed location.

Version 17.14.2-RC, released 2017-12-22:

  • Avoid NullReferenceException from preview in Power BI.

Version 17.14.0-RC, released 2017-12-22:

  • Add environment variable INVANTIVE_ADONET_LOG_FILE to control name of log file for Invantive Bridge.

Version 17.13.4-RC, released 2017-12-22:

  • Switch to new metadata structure of Invantive ADO.NET driver for translated table names.
  • 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