Downloads:

615,099

Downloads of v 2.1.3:

3,314

Last Update:

8/22/2018

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

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

Microsoft .NET Core - Windows Server Hosting

This is not the latest version of Microsoft .NET Core - Windows Server Hosting available.

2.1.3 | Updated: 8/22/2018

Downloads:

615,099

Downloads of v 2.1.3:

3,314

Software Author(s):

  • Microsoft

Microsoft .NET Core - Windows Server Hosting 2.1.3

This is not the latest version of Microsoft .NET Core - Windows Server Hosting available.

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

Requires IIS (Internet Information Services) to be installed

To install Microsoft .NET Core - Windows Server Hosting, run the following command from the command line or from PowerShell:

>

To upgrade Microsoft .NET Core - Windows Server Hosting, run the following command from the command line or from PowerShell:

>

To uninstall Microsoft .NET Core - Windows Server Hosting, 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 dotnetcore-windowshosting -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 dotnetcore-windowshosting -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 dotnetcore-windowshosting installed
  win_chocolatey:
    name: dotnetcore-windowshosting
    state: present
    version: 2.1.3
    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 'dotnetcore-windowshosting' do
  action    :install
  version  '2.1.3'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: dotnetcore-windowshosting,
    Version: 2.1.3,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller dotnetcore-windowshosting
{
   Name     = 'dotnetcore-windowshosting'
   Ensure   = 'Present'
   Version  = '2.1.3'
   Source   = 'STEP 3 URL'
}

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


package { 'dotnetcore-windowshosting':
  provider => 'chocolatey',
  ensure   => '2.1.3',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install dotnetcore-windowshosting version="2.1.3" 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 as a trusted package on 8/22/2018.

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_INSTALL_LTS_REDIST=0 OPT_INSTALL_FTS_REDIST=0). The package dotnetcore-runtime should be used to install the runtime 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):

  • Quiet - suppress display of native installer progress window (may be needed 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" dotnetcore-windowshosting


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 them 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-QuietRequested
{
    return $Env:chocolateyPackageParameters -like '*Quiet*'
}

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

Ensure-IisInstalled

$passiveOrQuiet = Get-PassiveOrQuietArgument -Scenario 'installation'
$arguments = @{
    packageName = $data.PackageName
    silentArgs = "$($data.AdditionalArgumentsToInstaller) /install /$passiveOrQuiet /norestart /log ""${Env:TEMP}\$($data.PackageName).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 = 'dotnetcore-windowshosting'
    Url = 'https://download.microsoft.com/download/6/E/B/6EBD972D-2E2F-41EB-9668-F73F5FDDC09C/dotnet-hosting-2.1.3-win.exe'
    Checksum = '7868ba46822b6e53c2a8056ec28f59434c7ecadb8e0adf8285396e12deb31cdec26158c54e4d0cad0566f8f7cb2f0612f685bd1ef20feb9e2864e36702e47116'
    ChecksumType = 'sha512'
    Url64 = 'https://download.microsoft.com/download/6/E/B/6EBD972D-2E2F-41EB-9668-F73F5FDDC09C/dotnet-hosting-2.1.3-win.exe'
    Checksum64 = '7868ba46822b6e53c2a8056ec28f59434c7ecadb8e0adf8285396e12deb31cdec26158c54e4d0cad0566f8f7cb2f0612f685bd1ef20feb9e2864e36702e47116'
    ChecksumType64 = 'sha512'
    AdditionalArgumentsToInstaller = 'OPT_INSTALL_LTS_REDIST=0 OPT_INSTALL_FTS_REDIST=0'
}

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 .NET Core - Windows Server Hosting 3.0.0-preview3-27503-5 334 Thursday, March 7, 2019 Approved
Microsoft .NET Core - Windows Server Hosting 3.0.0-preview-19075-0444 45 Friday, March 1, 2019 Approved
Microsoft .NET Core - Windows Server Hosting 2.2.7 5040 Tuesday, September 10, 2019 Approved
Microsoft .NET Core - Windows Server Hosting 2.2.6 14584 Tuesday, July 9, 2019 Approved
Microsoft .NET Core - Windows Server Hosting 2.2.5 39997 Tuesday, May 14, 2019 Approved
Microsoft .NET Core - Windows Server Hosting 2.2.4 174975 Wednesday, April 10, 2019 Approved
Microsoft .NET Core - Windows Server Hosting 2.2.3 27670 Thursday, March 14, 2019 Approved
Microsoft .NET Core - Windows Server Hosting 2.2.2 29967 Wednesday, February 13, 2019 Approved
Microsoft .NET Core - Windows Server Hosting 2.2.1 43709 Wednesday, January 9, 2019 Approved
Discussion for the Microsoft .NET Core - Windows Server Hosting Package

Ground Rules:

  • This discussion is only about Microsoft .NET Core - Windows Server Hosting and the Microsoft .NET Core - Windows Server Hosting 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 Core - Windows Server Hosting, 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