Downloads:

2,786

Downloads of v 17.1.2:

1,394

Last Update:

14 Aug 2017

Package Maintainer(s):

Software Author(s):

  • Nick Asseloos

Tags:

dotnetversiondetector admin

dotnetversiondetector (Install)

17.1.2 | Updated: 14 Aug 2017

Downloads:

2,786

Downloads of v 17.1.2:

1,394

Maintainer(s):

Software Author(s):

  • Nick Asseloos

Tags:

dotnetversiondetector admin

dotnetversiondetector (Install) 17.1.2

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install dotnetversiondetector (Install), run the following command from the command line or from PowerShell:

>

To upgrade dotnetversiondetector (Install), run the following command from the command line or from PowerShell:

>

To uninstall dotnetversiondetector (Install), 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 dotnetversiondetector -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 dotnetversiondetector -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 dotnetversiondetector installed
  win_chocolatey:
    name: dotnetversiondetector
    state: present
    version: 17.1.2
    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 'dotnetversiondetector' do
  action    :install
  version  '17.1.2'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: dotnetversiondetector,
    Version: 17.1.2,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller dotnetversiondetector
{
   Name     = 'dotnetversiondetector'
   Ensure   = 'Present'
   Version  = '17.1.2'
   Source   = 'STEP 3 URL'
}

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


package { 'dotnetversiondetector':
  provider => 'chocolatey',
  ensure   => '17.1.2',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install dotnetversiondetector version="17.1.2" 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 was approved as a trusted package on 09 Jul 2020.

Description

Detects and displays all .NET versions installed on the current machine. Can export to a file.
Utility itself does not use .NET so that it will work regardless of whether .NET is installed or what versions are installed.

tools\chocolateyinstall.ps1 

$ErrorActionPreference = 'Stop';

$packageName= 'dotnetversiondetector' # arbitrary name for the package, used in messages
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'EXE_MSI_OR_MSU' #only one of these: exe, msi, msu
  url           = "$toolsDir\netver.zip"
  url64bit      = "$toolsDir\netver.zip"
  #file         = "$toolsDir\netver.zip"

  softwareName  = 'dotnetversiondetector*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
  checksum      = 'B76345AE3B4AC1401E55149E5BE3CD81D0DAA8A2DD3E2F2318226A49E21C390A'
  checksumType  = 'sha256' #default is md5, can also be sha1, sha256 or sha512
  checksum64    = 'B76345AE3B4AC1401E55149E5BE3CD81D0DAA8A2DD3E2F2318226A49E21C390A'
  checksumType64= 'sha256' #default is checksumType
}

Install-ChocolateyZipPackage @packageArgs # https://chocolatey.org/docs/helpers-install-chocolatey-zip-package

Move-Item $toolsdir\dotnet.exe $toolsdir\dotnetversions.exe -Force


Write-Output ""
Write-Output "**********************************************************************************************************"
Write-Output "*  INSTRUCTIONS: At a shell prompt, type 'dotnetversions' to start the dot net version detector utility          *"
Write-Output "**********************************************************************************************************"
Write-Output ""
tools\LICENSE.txt 
From: <insert applicable license url here>

LICENSE
The only hint at a license is the statement on the product home page to send an email to request redistribution rights.

The authors response to this request is below.

---------- Forwarded message ----------
From: ASoft Info <[email protected]>
Date: Mon, Nov 7, 2016 at 12:01 PM
Subject: RE: Permission to Redistribute Or...
To: darwin*******.com


Hi Darwin,

Sure, I grant you permission to distribute it however it fits you best.

Thank you for informing me; too bad that the names clash now.
I will see if I find another solution because this will clash with people/companies that distribute/call it from their applications/frameworks.
I will have a look at the new CLI to see how it is now.

Thank you & best regards,
Nick
tools\netver.zip 
md5: 0D1257A83CD6689BAC91C33794CA6F9B | sha1: 4BEC2ED3C7E2F0558323DA8372487F77F8789AFC | sha256: B76345AE3B4AC1401E55149E5BE3CD81D0DAA8A2DD3E2F2318226A49E21C390A | sha512: 503B53CE0C1027CC36B906144C973CE31C76546DB48A281D1DB69899ED9A9378767FDE73AC8EE11C6C65CD216A024C40E99D8E4FB75AEC562A7C4BFC057A81E5
tools\VERIFICATION.txt 

Note: Include this file if including binaries you have the right to distribute.
Otherwise delete. this file.

===DELETE ABOVE THIS LINE AND THIS LINE===

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The appropriate checksum for the package has been encoded in the normal checksum fields in chocolateyinstall.ps1.

This means that the package will display "hashes match" even though the source installer is embedded.

To verify, execute "Get-FileHash netver.zip -algorithm sha1" and compare the output value to that in chocolateyinstall.ps1

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
dotnetversiondetector (Install) 17.1.2 1394 Monday, August 14, 2017 Approved
dotnetversiondetector (Install) 16.3.2.20170323 390 Thursday, March 23, 2017 Approved
dotnetversiondetector (Install) 16.3.2 349 Monday, February 20, 2017 Approved
DotNET Version Detector 15.0 536 Saturday, January 2, 2016 Approved

Packaging Version 16.3.2.20170323
- renames exe from default of dotnet.exe to dotnetversions.exe to avoid clashes with dotnet CLI.
Supports up through .NET 4.6.2

This package has no dependencies.

Discussion for the dotnetversiondetector (Install) Package

Ground Rules:

  • This discussion is only about dotnetversiondetector (Install) and the dotnetversiondetector (Install) 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 dotnetversiondetector (Install), 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