Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

891,996

Downloads of v 4.7.2.20190225:

347,439

Last Update:

26 Feb 2019

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

microsoft .net framework 4.7.2 developer target targeting pack multi dotnet netfx admin

Microsoft .NET Framework 4.7.2 Developer Pack

This is not the latest version of Microsoft .NET Framework 4.7.2 Developer Pack available.

  • 1
  • 2
  • 3

4.7.2.20190225 | Updated: 26 Feb 2019

Downloads:

891,996

Downloads of v 4.7.2.20190225:

347,439

Maintainer(s):

Software Author(s):

  • Microsoft

Microsoft .NET Framework 4.7.2 Developer Pack 4.7.2.20190225

This is not the latest version of Microsoft .NET Framework 4.7.2 Developer Pack available.

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Microsoft. The inclusion of Microsoft trademark(s), if any, upon this webpage is solely to identify Microsoft goods or services and not for commercial purposes.

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Exemption:

Dependency requires reboot

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Microsoft .NET Framework 4.7.2 Developer Pack, run the following command from the command line or from PowerShell:

>

To upgrade Microsoft .NET Framework 4.7.2 Developer Pack, run the following command from the command line or from PowerShell:

>

To uninstall Microsoft .NET Framework 4.7.2 Developer Pack, 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 netfx-4.7.2-devpack -y --source="'INTERNAL REPO URL'" --version="'4.7.2.20190225'" [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 netfx-4.7.2-devpack -y --source="'INTERNAL REPO URL'" --version="'4.7.2.20190225'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install netfx-4.7.2-devpack
  win_chocolatey:
    name: netfx-4.7.2-devpack
    version: '4.7.2.20190225'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'netfx-4.7.2-devpack' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '4.7.2.20190225'
end

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


cChocoPackageInstaller netfx-4.7.2-devpack
{
    Name     = "netfx-4.7.2-devpack"
    Version  = "4.7.2.20190225"
    Source   = "INTERNAL REPO URL"
}

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


package { 'netfx-4.7.2-devpack':
  ensure   => '4.7.2.20190225',
  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.

NOTE

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

Package Approved

This package was approved as a trusted package on 26 Feb 2019.

Description

The .NET Framework 4.7.2 Developer Pack lets developers build applications that target the .NET Framework 4.7.2 by using Visual Studio 2017, Visual Studio 2015 or other IDEs. This is a single package that bundles the .NET Framework 4.7.2, the .NET 4.7.2 Targeting Pack, and the .NET Framework 4.7.2 SDK.


tools\ChocolateyInstall.ps1
. (Join-Path -Path (Split-Path -Parent -Path $MyInvocation.MyCommand.Definition) -ChildPath 'DotNetDevPackHelpers.ps1')

$version = '4.7.2'
$arguments = @{
    PackageName = 'netfx-4.7.2-devpack'
    Version = $version
    ProductNameWithVersion = "Microsoft .NET Framework $version Developer Pack"
    Url = 'https://download.microsoft.com/download/3/B/F/3BFB9C35-405D-45DF-BDAF-0EB57D047888/NDP472-DevPack-ENU.exe'
    Checksum = '2F4EE2852B95C37A806E2DEEC567751DD59B0DD27049641BBD4E1C0E22ADFE46'
    ChecksumType = 'sha256'
}

Install-DotNetDevPack @arguments
tools\DotNetDevPackHelpers.ps1
$scriptDirectory = Split-Path -Parent -Path $MyInvocation.MyCommand.Definition
. (Join-Path -Path $scriptDirectory -ChildPath 'Get-NativeInstallerExitCode.ps1')
. (Join-Path -Path $scriptDirectory -ChildPath 'Install-ChocolateyInstallPackageAndHandleExitCode.ps1')
. (Join-Path -Path $scriptDirectory -ChildPath 'Set-PowerShellExitCode.ps1')

function Get-SafeLogPath
{
    $logPath = $Env:TEMP
    if ($logPath -like '\\*')
    {
        # .NET installer does not like logging to a network share (https://github.com/jberezanski/ChocolateyPackages/issues/15)
        $candidates = @("$Env:LOCALAPPDATA\Temp\chocolatey", "$Env:LOCALAPPDATA\Temp", "$Env:USERPROFILE\AppData\Local\Temp\chocolatey", "$Env:USERPROFILE\AppData\Local\Temp", "$Env:SystemRoot\TEMP", $scriptDirectory)
        foreach ($candidate in $candidates)
        {
            if ((Test-Path -Path $candidate) -and $candidate -notlike '\\*')
            {
                Write-Verbose "Using '$candidate' as log path because `$Env:TEMP points to a network share, which may cause the installation to fail"
                $logPath = $candidate
                break
            }
        }
    }

    return $logPath
}

function Test-Installed($Release)
{
    $props = Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -Name Release -ErrorAction SilentlyContinue
    return $props -ne $null -and $props.Release -ge $Release
}

function Get-DefaultChocolateyLocalFilePath
{
    [CmdletBinding()]
    Param
    (
        [Parameter(Mandatory = $true)] [string] $OriginalFileName
    )

    # adapted from Install-ChocolateyPackage 0.10.8
    $chocTempDir = $env:TEMP
    $tempDir = Join-Path $chocTempDir "$($env:chocolateyPackageName)"
    if ($env:chocolateyPackageVersion -ne $null) { $tempDir = Join-Path $tempDir "$($env:chocolateyPackageVersion)"; }
    $tempDir = $tempDir -replace '\\chocolatey\\chocolatey\\', '\chocolatey\'
    if (![System.IO.Directory]::Exists($tempDir)) { [System.IO.Directory]::CreateDirectory($tempDir) | Out-Null }
    $downloadFilePath = Join-Path $tempDir $OriginalFileName
    Write-Debug "Local file path: $downloadFilePath"
    return $downloadFilePath
}

function Invoke-CommandWithTempPath
{
    [CmdletBinding()]
    Param
    (
        [Parameter(Mandatory = $true)] [string] $TempPath,
        [Parameter(Mandatory = $true)] [scriptblock] $ScriptBlock
    )

    $oldTemp = $Env:TEMP
    if ($Env:TEMP -ne $TempPath)
    {
        Write-Debug "Changing `$Env:TEMP from '$oldTemp' to '$TempPath'"
        $Env:TEMP = $TempPath
    }

    try
    {
        & $ScriptBlock
    }
    finally
    {
        if ($Env:TEMP -ne $oldTemp)
        {
            Write-Debug "Changing `$Env:TEMP back to '$oldTemp'"
            $Env:TEMP = $oldTemp
        }
    }
}

function Install-DotNetDevPack
{
    [CmdletBinding(PositionalBinding = $false)]
    Param
    (
        [Parameter(Mandatory = $true)] [string] $PackageName, # = 'netfx-4.8-devpack'
        [Parameter(Mandatory = $true)] $Version, # = '4.8'
        [Parameter(Mandatory = $true)] $ProductNameWithVersion, # = "Microsoft .NET Framework $version Developer Pack early access build 3745"
        [Parameter(Mandatory = $true)] $Url, # = 'https://download.visualstudio.microsoft.com/download/pr/9854b5f2-2341-4136-ad7d-1d881ab8d603/e3a011f2a41a59b086f78d64e1c7a3fc/NDP48-DevPack-ENU.exe'
        [Parameter(Mandatory = $true)] $Checksum, # = '67979C8FBA2CD244712A31A7FE323FD8BD69AA7971F152F8233CB109A7260F06'
        [Parameter(Mandatory = $true)] $ChecksumType # = 'sha256'
    )

    $originalFileName = Split-Path -Leaf -Path ([uri]$url).LocalPath
    $downloadFilePath = Get-DefaultChocolateyLocalFilePath -OriginalFileName $originalFileName
    $downloadArguments = @{
        packageName = $packageName
        fileFullPath = $downloadFilePath
        url = $url
        checksum = $checksum
        checksumType = $checksumType
        url64 = $url
        checksum64 = $checksum
        checksumType64 = $checksumType
    }

    Get-ChocolateyWebFile @downloadArguments | Out-Null

    $ERROR_SUCCESS = 0
    $ERROR_SUCCESS_REBOOT_REQUIRED = 3010
    $STATUS_ACCESS_VIOLATION = 0xC0000005

    $safeLogPath = Get-SafeLogPath
    $installerExeArguments = @{
        packageName = $packageName
        fileType = 'exe'
        file = $downloadFilePath
        silentArgs = ('/Quiet /NoRestart /Log "{0}\{1}_{2}_{3:yyyyMMddHHmmss}.log"' -f $safeLogPath, $packageName, $version, (Get-Date))
        validExitCodes = @(
            $ERROR_SUCCESS # success
            $ERROR_SUCCESS_REBOOT_REQUIRED # success, restart required
        )
    }

    $exitCodeHandler = {
        $installResult = $_
        $exitCode = $installResult.ExitCode
        if ($exitCode -eq $ERROR_SUCCESS_REBOOT_REQUIRED)
        {
            Write-Warning "$productNameWithVersion has been installed, but a reboot is required to finalize the installation. Until the computer is rebooted, dependent packages may fail to install or function properly."
        }
        elseif ($exitCode -eq $ERROR_SUCCESS)
        {
            Write-Verbose "$productNameWithVersion has been installed successfully, a reboot is not required."
        }
        elseif ($exitCode -eq $null)
        {
            Write-Warning "Package installation has finished, but this Chocolatey version does not provide the installer exit code. A restart may be required to finalize $productNameWithVersion installation."
        }
        elseif ($exitCode -eq $STATUS_ACCESS_VIOLATION)
        {
            # installer crash (access violation), but may occur at the very end, after the devpack is installed
            if (Test-Path -Path 'Env:\ProgramFiles(x86)')
            {
                $programFiles32 = ${Env:ProgramFiles(x86)}
            }
            else
            {
                $programFiles32 = ${Env:ProgramFiles}
            }

            $mscorlibPath = "$programFiles32\Reference Assemblies\Microsoft\Framework\.NETFramework\v${version}\mscorlib.dll"
            Write-Warning "The native installer crashed, checking if it managed to install the devpack before the crash"
            Write-Debug "Testing existence of $mscorlibPath"
            if (Test-Path -Path $mscorlibPath)
            {
                Write-Verbose "mscorlib.dll found: $mscorlibPath"
                Write-Verbose 'This probably means the devpack got installed successfully, despite the installer crash'
                $installResult.ShouldFailInstallation = $false
                $installResult.ExitCode = $ERROR_SUCCESS # to avoid triggering failure detection in choco.exe
            }
            else
            {
                Write-Verbose "mscorlib.dll not found in expected location: $mscorlibPath"
                Write-Verbose 'This probably means the installer crashed before it could fully install the devpack'
            }
        }
    }

    Invoke-CommandWithTempPath -TempPath $safeLogPath -ScriptBlock { Install-ChocolateyInstallPackageAndHandleExitCode @installerExeArguments -ExitCodeHandler $exitCodeHandler }
}
tools\Get-NativeInstallerExitCode.ps1
<#
.SYNOPSIS
    Returns the exit code set earlier by a native installer executed via the Start-ChocolateyProcessAsAdmin helper.

.OUTPUT
    System.Int32 or $null
#>
function Get-NativeInstallerExitCode
{
    [CmdletBinding()]
    Param
    (
    )
    End
    {
        $exitCodeString = Get-EnvironmentVariable -Name ChocolateyExitCode -Scope Process
        if ([string]::IsNullOrEmpty($exitCodeString))
        {
            return $null
        }

        [int] $exitCode = 0
        if (-not ([int]::TryParse($exitCodeString, [ref]$exitCode)))
        {
            Write-Warning "Unable to parse ChocolateyExitCode value: $exitCodeString"
            return $null
        }

        return $exitCode
    }
}
tools\Install-ChocolateyInstallPackageAndHandleExitCode.ps1
function Install-ChocolateyInstallPackageAndHandleExitCode
{
    [CmdletBinding()]
    Param
    (
        # parameters of Install-ChocolateyInstallPackage (slightly modified to be more strict)
        [parameter(Mandatory=$true)][string] $packageName,
        [parameter(Mandatory=$true)][alias("installerType","installType")][string] $fileType,
        [parameter(Mandatory=$false)][string[]] $silentArgs = '',
        [parameter(Mandatory=$false)][alias("fileFullPath")][string] $file,
        [parameter(Mandatory=$false)][alias("fileFullPath64")][string] $file64,
        [parameter(Mandatory=$false)][int[]] $validExitCodes = @(0),
        [parameter(Mandatory=$false)][alias("useOnlyPackageSilentArgs")][switch] $useOnlyPackageSilentArguments = $false,
        [parameter(Mandatory=$false)][switch] $useOriginalLocation,
        # new parameters
        [Parameter(Mandatory=$false)][ScriptBlock] $ExitCodeHandler,
        [Parameter(Mandatory=$false)][switch] $PassThru
    )
    Begin
    {
        Set-StrictMode -Version 2
        $ErrorActionPreference = 'Stop'
    }
    End
    {
        $exitCode = $null
        $invalidExitCodeErrorMessage = $null
        Set-StrictMode -Off
        try
        {
            # Start-ChocolateyProcessAsAdmin, invoked indirectly by Install-ChocolateyInstallPackage,
            # overwrites a few arbitrary exit codes with 0. The only execution path
            # which faithfully preserves the original exit code is the error path.
            # Pass only 0 as a valid exit code and catch the error thrown when
            # the exit code is "invalid".
            $arguments = @{}
            $parametersToRemove = @('validExitCodes', 'ExitCodeHandler', 'PassThru')
            $PSBoundParameters.GetEnumerator() | Where-Object { $parametersToRemove -notcontains $_.Key } | ForEach-Object { $arguments[$_.Key] = $_.Value }
            Install-ChocolateyInstallPackage `
                -validExitCodes @(0) `
                @arguments
        }
        catch [System.Management.Automation.RuntimeException]
        {
            if ($_.Exception.Message -notlike '*Running * was not successful. Exit code was*')
            {
                throw
            }

            $invalidExitCodeErrorMessage = $_.Exception.Message
        }
        finally
        {
            Set-StrictMode -Version 2
        }

        $exitCode = Get-NativeInstallerExitCode
        if ($exitCode -eq $null -and $invalidExitCodeErrorMessage -ne $null)
        {
            # 0.10.1 "Running [`"$exeToRun`" $wrappedStatements] was not successful. Exit code was '$exitCode'. See log for possible error messages."
            # 0.9.10-rc1 "Running [`"$exeToRun`" $statements] was not successful. Exit code was '$exitCode'. See log for possible error messages."
            # 0.9.9-beta3 "[ERROR] Running $exeToRun with $statements was not successful. Exit code was `'$($s.ExitCode)`' Error Message: $innerError."
            # 0.9.9-alpha "[ERROR] Running $exeToRun with $statements was not successful. Exit code was `'$($s.ExitCode)`'."
            # 0.9.8.28-alpha2 - 0.9.8.33 "[ERROR] Running $exeToRun with $statements was not successful. Exit code was `'$($s.ExitCode)`' Error Message: $innerError."
            # 0.9.8.17-alpha1 "[ERROR] Running $exeToRun with $statements was not successful. Exit code was `'$($s.ExitCode)`'."
            # 0.9.8.16? "[ERROR] Running $exeToRun with $statements was not successful. Exit code was `'$($s.ExitCode)`'."
            # earlier "[ERROR] Running $exeToRun with $statements was not successful."
            Write-Verbose 'Running on Chocolatey version which does not expose the native installer exit code (probably earlier than 0.9.10). Attempting to parse the exit code out of the error message.'
            Write-Verbose "Error message from Install-ChocolateyPackage: $invalidExitCodeErrorMessage"
            $rxExitCode = 'Running\ .+\ was\ not\ successful\.\ Exit\ code\ was\ ''(?<exitCode>-?\d+)'''
            if ($invalidExitCodeErrorMessage -match $rxExitCode)
            {
                $exitCodeString = $matches['exitCode']
                try
                {
                    $exitCode = [int]::Parse($exitCodeString)
                    Write-Verbose "Exit code determined from the error message: $exitCode"
                }
                catch
                {
                    Write-Verbose "Unable to parse the exit code string ($exitCodeString): $($_.Exception)"
                }
            }

            if ($exitCode -eq $null)
            {
                # are we running PowerShell Chocolatey?
                if ($Env:ChocolateyInstall -ne $null -and (Test-Path -Path (Join-Path -Path $Env:ChocolateyInstall -ChildPath 'chocolateyInstall\chocolatey.ps1')))
                {
                    Write-Warning 'This Chocolatey version does not provide a way to determine the installation result (exit code). Please upgrade to a newer version (at least 0.9.8.17).'
                }
                else
                {
                    Write-Warning 'Unable to determine the installation result (exit code). Please contact the maintainers of the ''chocolatey-windowsupdate.extension'' package.'
                }
            }
        }

        $shouldFail = $exitCode -ne $null -and ($validExitCodes | Measure-Object).Count -gt 0 -and $validExitCodes -notcontains $exitCode
        if ($invalidExitCodeErrorMessage -eq $null)
        {
            $errorMessage = "Installation of $packageName was not successful (exit code: $exitCode)."
        }
        else
        {
            $errorMessage = $invalidExitCodeErrorMessage
        }

        if ($ExitCodeHandler -ne $null)
        {
            $context = New-Object -TypeName PSObject -Property @{ ExitCode = $exitCode; ErrorMessage = $errorMessage; ShouldFailInstallation = $shouldFail }
            $_ = $context
            & $exitCodeHandler

            $shouldFail = $context.ShouldFailInstallation -eq $true
            $shouldGenerateErrorMessage = $false
            if ($context.ExitCode -ne $null -and $context.ExitCode -ne $exitCode)
            {
                $exitCode = $context.ExitCode
                Set-PowerShellExitCode -ExitCode $exitCode
                $shouldGenerateErrorMessage = $true
            }

            if ($context.ErrorMessage -ne $null -and $context.ErrorMessage -ne $errorMessage)
            {
                $errorMessage = $context.ErrorMessage
                $shouldGenerateErrorMessage = $false
            }

            if ($shouldGenerateErrorMessage)
            {
                $errorMessage = "Installation of $packageName was not successful (exit code: $exitCode)."
            }
        }

        if ($shouldFail)
        {
            throw $errorMessage
        }
        else
        {
            # prevent failure on PowerShell Chocolatey
            $failureLogPath = "$Env:TEMP\chocolatey\$packageName\failure.log"
            if (Test-Path -Path $failureLogPath)
            {
                Write-Verbose "Renaming file $failureLogPath so that Chocolatey does not treat the installation as failed"
                Rename-Item -Path $failureLogPath -NewName 'failure.old.log' -Force
            }
        }

        if ($PassThru)
        {
            $result = New-Object -TypeName PSObject -Property @{ ExitCode = $exitCode; ErrorMessage = $errorMessage }
            return $result
        }
    }
}
tools\Set-PowerShellExitCode.ps1
function Set-PowerShellExitCode
{
    [CmdletBinding()]
    Param
    (
        [Parameter(Mandatory = $true)] [int] $ExitCode
    )
    End
    {
        chocolateyInstaller\Set-PowerShellExitCode @PSBoundParameters
        if ($ExitCode -eq 0 -and $Env:ChocolateyExitCode -ne '0')
        {
            Write-Debug 'chocolateyInstaller\Set-PowerShellExitCode ignored 0, setting the host exit code and environment variable manually'
            $Host.SetShouldExit(0)
            $Env:ChocolateyExitCode = '0'
        }
    }
}

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
Microsoft .NET Framework 4.7.2 Developer Pack 4.7.2.20190225 347439 Tuesday, February 26, 2019 Approved
Microsoft .NET Framework 4.7.2 Developer Pack 4.7.2.20180712 354135 Thursday, July 12, 2018 Approved
Microsoft .NET Framework 4.7.2 Developer Pack 4.7.2.0 3270 Thursday, May 3, 2018 Approved
Microsoft .NET Framework 4.7.2 Developer Pack 4.7.2.0-preview1 388 Saturday, March 17, 2018 Exempted

Software

.NET Framework 4.7.2 announcement
.NET Framework 4.7.2 readme
.NET Framework 4.7.2 changes

Package

4.7.2.20190225: Implemented workaround for native installer crash under WinRM/DSC (https://github.com/jberezanski/ChocolateyPackages/issues/22).


Discussion for the Microsoft .NET Framework 4.7.2 Developer Pack Package

Ground Rules:

  • This discussion is only about Microsoft .NET Framework 4.7.2 Developer Pack and the Microsoft .NET Framework 4.7.2 Developer Pack 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 Microsoft .NET Framework 4.7.2 Developer Pack, 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