Downloads:

1,262

Downloads of v 12.2.19109:

507

Last Update:

06 Nov 2020

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

microsoft .net core runtime redistributable asp.net module ancm iis admin

Microsoft ASP.NET Core Module V1

  • 1
  • 2
  • 3

12.2.19109 | Updated: 06 Nov 2020

Downloads:

1,262

Downloads of v 12.2.19109:

507

Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
Microsoft ASP.NET Core Module V1 12.2.19109

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Exemption:

Requires IIS

Details

Scan Testing Successful:

No detections found in any package files

Details

To install Microsoft ASP.NET Core Module V1, run the following command from the command line or from PowerShell:

>

To upgrade Microsoft ASP.NET Core Module V1, run the following command from the command line or from PowerShell:

>

To uninstall Microsoft ASP.NET Core Module V1, 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://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. Enter your internal repository url

(this should look similar to https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade dotnet-aspnetcoremodule-v1 -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 dotnet-aspnetcoremodule-v1 -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 dotnet-aspnetcoremodule-v1 installed
  win_chocolatey:
    name: dotnet-aspnetcoremodule-v1
    state: present
    version: 12.2.19109
    source: STEP 3 URL

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


chocolatey_package 'dotnet-aspnetcoremodule-v1' do
  action    :install
  version  '12.2.19109'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: dotnet-aspnetcoremodule-v1,
    Version: 12.2.19109,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller dotnet-aspnetcoremodule-v1
{
   Name     = 'dotnet-aspnetcoremodule-v1'
   Ensure   = 'Present'
   Version  = '12.2.19109'
   Source   = 'STEP 3 URL'
}

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


package { 'dotnet-aspnetcoremodule-v1':
  provider => 'chocolatey',
  ensure   => '12.2.19109',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install dotnet-aspnetcoremodule-v1 version="12.2.19109" 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.

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

This package was approved by moderator mkevenaar on 10 Nov 2020.

Description

.NET Core is a general purpose development platform maintained by Microsoft and the .NET community on GitHub. It is cross-platform, supporting Windows, macOS and Linux, and can be used in device, cloud, and embedded/IoT scenarios.

This package installs the ASP.NET Core Module for IIS, enabling running of ASP.NET Core applications. IIS must be enabled prior to installing this package. ASP.NET Core does not use any managed IIS modules, so no ASP.NET IIS features need to be enabled.

The native installer is instructed to skip installing the .NET Core Runtime (OPT_NO_RUNTIME=1) and the ASP.NET Core Runtime and Shared Framework (OPT_NO_SHAREDFX=1). The packages dotnetcore-runtime and dotnetcore-aspnetruntime should be used to install these runtimes when hosting "portable" ASP.NET Core applications (which use the machine-wide runtime). Hosting of "self-contained" ASP.NET Core applications does not require the runtime to be installed, because those applications include the desired runtime as part of their binaries.

The package supports the following parameters (--package-parameters, --params):

  • Passive - display native installer progress window (may not work on Server Core)
  • IgnoreMissingIIS - allow package installation even if IIS is not present (probably useless, as the native installer will not install anything)

Example: cinst -y --params="Quiet IgnoreMissingIIS" dotnet-aspnetcoremodule-v1


tools\ChocolateyInstall.ps1
$ErrorActionPreference = 'Stop'
Set-StrictMode -Version 2

$data = & (Join-Path -Path (Split-Path -Path $MyInvocation.MyCommand.Path) -ChildPath data.ps1)

function Get-DismPath
{
    # .NET Core supports Windows 7 or later - this aligns nicely with dism.exe availability
    $dism = Join-Path -Path $Env:SystemRoot -ChildPath 'System32\dism.exe'
    if (-not (Test-Path -Path $dism)) {
        throw 'Windows 7 / Server 2008 R2 or later is required.'
    }
    return $dism
}

function Test-IisInstalled
{
    $dism = Get-DismPath
    $iisState = 'Unknown'
    & $dism /English /Online /Get-FeatureInfo /FeatureName:IIS-WebServer | Tee-Object -Variable dismOutput | Select-String -Pattern '^State : (\w+)$' | ForEach-Object { $iisState = $_.Matches[0].Groups[1].Value }
    if ($LastExitCode -ne 0) {
        Write-Warning "Unable to determine IIS installation state (dism.exe exit code: $LastExitCode)"
        Write-Warning 'dism.exe output:'
        $dismOutput | Write-Warning
    } else {
        Write-Debug 'dism.exe output:'
        $dismOutput | Write-Debug
    }
    $iisInstalled = $iisState -eq 'Enabled'
    return $iisInstalled
}

function Ensure-IisInstalled
{
    $iisInstalled = Test-IisInstalled

    if (-not $iisInstalled) {
        $ignoreMissingIisKeyword = 'IgnoreMissingIIS'
        if ($Env:chocolateyPackageParameters -notlike "*$ignoreMissingIisKeyword*") {
            throw "IIS is not installed. Install at least one of IIS components, such as IIS-StaticContent, before installing this package, or pass '$ignoreMissingIisKeyword' as package parameter to force the installation anyway."
        } else {
            Write-Warning "IIS is not installed, but proceeding with the installation because '$ignoreMissingIisKeyword' was passed as package parameter."
        }
    }

    if ($iisInstalled) {
        Write-Verbose 'IIS is enabled.'
    } else {
        Write-Warning 'IIS is not enabled. The ASP.NET Core Module for IIS requires IIS to be enabled before installing the module. To install the module, enable IIS and install this package again using the --force switch.'
    }
}

function Test-PassiveRequested
{
    return $Env:chocolateyPackageParameters -like '*Passive*'
}

function Get-PassiveOrQuietArgument
{
    [CmdletBinding()]
    Param (
        [string] $Scenario = 'installation'
    )
    if (Test-PassiveRequested) {
        Write-Verbose "Performing an $Scenario with visible progress window, as requested."
        $passiveOrQuiet = 'passive'
    } else {
        Write-Verbose "Performing a quiet $Scenario (default)."
        $passiveOrQuiet = 'quiet'
    }
    return $passiveOrQuiet
}

Ensure-IisInstalled

$passiveOrQuiet = Get-PassiveOrQuietArgument -Scenario 'installation'
$arguments = @{
    packageName = $data.PackageName
    silentArgs = "$($data.AdditionalArgumentsToInstaller) /install /$passiveOrQuiet /norestart /log ""${Env:TEMP}\$($data.PackageName)-$(Get-Date -Format 'yyyyMMddHHmmss').log"""
    validExitCodes = @(
        0, # success
        3010 # success, restart required
    )
    url = $data.Url
    checksum = $data.Checksum
    checksumType = $data.ChecksumType
    url64 = $data.Url64
    checksum64 = $data.Checksum64
    checksumType64 = $data.ChecksumType64
}

Set-StrictMode -Off
Install-ChocolateyPackage @arguments
tools\data.ps1
@{
    PackageName = 'dotnet-aspnetcoremodule-v1'
    Url = 'https://download.visualstudio.microsoft.com/download/pr/ba001109-03c6-45ef-832c-c4dbfdb36e00/e3413f9e47e13f1e4b1b9cf2998bc613/dotnet-hosting-2.2.8-win.exe'
    Checksum = '1b3177fc65ec343f641b8ffdc2a0e925e322e90ed44dcb5c6d3982a370dd7b56f7fcc362dad3a4b7e2db4f0fe6878b7e7448fc7f41dfe01302c7484434691f6b'
    ChecksumType = 'sha512'
    Url64 = 'https://download.visualstudio.microsoft.com/download/pr/ba001109-03c6-45ef-832c-c4dbfdb36e00/e3413f9e47e13f1e4b1b9cf2998bc613/dotnet-hosting-2.2.8-win.exe'
    Checksum64 = '1b3177fc65ec343f641b8ffdc2a0e925e322e90ed44dcb5c6d3982a370dd7b56f7fcc362dad3a4b7e2db4f0fe6878b7e7448fc7f41dfe01302c7484434691f6b'
    ChecksumType64 = 'sha512'
    AdditionalArgumentsToInstaller = 'OPT_NO_RUNTIME=1 OPT_NO_SHAREDFX=1' # these arguments are valid for .NET Core 2.1+
}

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
Microsoft ASP.NET Core Module V1 12.1.21105 42 Tuesday, May 11, 2021 Approved
Microsoft ASP.NET Core Module V1 12.1.21076 145 Wednesday, April 14, 2021 Approved
Microsoft ASP.NET Core Module V1 12.1.21053 145 Wednesday, March 10, 2021 Approved
Microsoft ASP.NET Core Module V1 12.1.21021 131 Wednesday, February 10, 2021 Approved
Microsoft ASP.NET Core Module V1 12.1.20325 82 Tuesday, January 12, 2021 Approved
Microsoft ASP.NET Core Module V1 12.1.20266 210 Thursday, November 5, 2020 Approved

Software

.NET Core 2.2.8 Release Notes

Package

This package version installs ASP.NET Core Module version 12.2.19109.5.

Discussion for the Microsoft ASP.NET Core Module V1 Package

Ground Rules:

  • This discussion is only about Microsoft ASP.NET Core Module V1 and the Microsoft ASP.NET Core Module V1 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 ASP.NET Core Module V1, 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