Ansible
PS DSC
Downloads:
1,763,076
Downloads of v 2.0.5.20180111:
6,391
Last Update:
11 Jan 2018
Package Maintainer(s):
Software Author(s):
- Microsoft
Tags:
- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Microsoft .NET Core - Windows Server Hosting
This is not the latest version of Microsoft .NET Core - Windows Server Hosting available.
- 1
- 2
- 3
2.0.5.20180111 | Updated: 11 Jan 2018
- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
1,763,076
Downloads of v 2.0.5.20180111:
6,391
Maintainer(s):
Software Author(s):
- Microsoft
Microsoft .NET Core - Windows Server Hosting 2.0.5.20180111
This is not the latest version of Microsoft .NET Core - Windows Server Hosting 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
Deployment Method: Individual Install, Upgrade, & Uninstall
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:
Deployment Method:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download dotnetcore-windowshosting --internalize --version=2.0.5.20180111 --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade dotnetcore-windowshosting -y --source="'INTERNAL REPO URL'" --version="'2.0.5.20180111'" [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="'INTERNAL REPO URL'" --version="'2.0.5.20180111'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install dotnetcore-windowshosting
win_chocolatey:
name: dotnetcore-windowshosting
version: '2.0.5.20180111'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'dotnetcore-windowshosting' do
action :install
source 'INTERNAL REPO URL'
version '2.0.5.20180111'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller dotnetcore-windowshosting
{
Name = "dotnetcore-windowshosting"
Version = "2.0.5.20180111"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'dotnetcore-windowshosting':
ensure => '2.0.5.20180111',
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.
This package was approved as a trusted package on 11 Jan 2018.
.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 and/or IIS Express, enabling running of ASP.NET Core applications. IIS must be enabled and/or IIS Express must be installed 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 neither full IIS nor IIS Express is present (probably useless, as the native installer will not install anything)
Example: cinst -y --params="Quiet IgnoreMissingIIS" dotnetcore-windowshosting
$ErrorActionPreference = 'Stop'
Set-StrictMode -Version 2
$data = & (Join-Path -Path (Split-Path -Path $MyInvocation.MyCommand.Path) -ChildPath data.ps1)
function Uninstall-ApplicationPackage
{
[CmdletBinding()]
param(
[string] $PackageName,
[string] $ApplicationName,
[string] $UninstallerName,
[string] $ArgumentsToUninstaller,
[int[]] $ValidExitCodes
)
$informMaintainer = "Please report this to the maintainer of this package ($PackageName)."
Set-StrictMode -Off
$unfilteredUninstallKeys = Get-UninstallRegistryKey -SoftwareName $ApplicationName
Set-StrictMode -Version 2
$uninstallKey = $unfilteredUninstallKeys | Where-Object { $_ -ne $null -and ($_.PSObject.Properties['SystemComponent'] -eq $null -or $_.SystemComponent -ne 1) }
$count = ($uninstallKey | Measure-Object).Count
Write-Debug "Found $count Uninstall key(s)"
if ($count -eq 0)
{
Write-Warning "Uninstall information for $ApplicationName could not be found. This probably means the application was uninstalled outside Chocolatey."
return
}
if ($count -gt 1)
{
throw "More than one Uninstall key found for $ApplicationName! $informMaintainer"
}
$uninstallKey = $uninstallKey | Select-Object -First 1
# in PS 2.0, casting to [array] done inside Get-UninstallRegistryKey strips the PS* properties
if ($uninstallKey.PSObject.Properties['PSPath'] -ne $null)
{
Write-Debug "Using Uninstall key: $($uninstallKey.PSPath)"
}
$uninstallString = $uninstallKey.UninstallString
Write-Debug "UninstallString: $uninstallString"
if (-not ($uninstallString -match '^\s*(\"[^\"]+\")|([^\s]+)'))
{
throw "UninstallString '$uninstallString' is not of the expected format. $informMaintainer"
}
$uninstallerPath = $matches[0].Trim('"')
Write-Debug "uninstallerPath: $uninstallerPath"
if ((Split-Path -Path $uninstallerPath -Leaf) -notlike $UninstallerName)
{
throw "The uninstaller file name is unexpected (uninstallerPath: $uninstallerPath). $informMaintainer"
}
$arguments = @{
PackageName = $PackageName
FileType = 'exe'
SilentArgs = $ArgumentsToUninstaller
ValidExitCodes = $ValidExitCodes
File = $uninstallerPath
}
$argumentsDump = ($arguments.GetEnumerator() | % { '-{0}:''{1}''' -f $_.Key,"$($_.Value)" }) -join ' '
Write-Debug "Uninstall-ChocolateyPackage $argumentsDump"
Uninstall-ChocolateyPackage @arguments
}
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
}
$passiveOrQuiet = Get-PassiveOrQuietArgument -Scenario 'uninstallation'
$arguments = @{
PackageName = $data.PackageName
ApplicationName = $data.ApplicationName
UninstallerName = $data.UninstallerName
ArgumentsToUninstaller = "/uninstall /$passiveOrQuiet /norestart /log ""${Env:TEMP}\$($data.PackageName)_uninstall.log"""
ValidExitCodes = @(
0, # success
3010 # success, restart required
)
}
Uninstall-ApplicationPackage @arguments
@{
PackageName = 'dotnetcore-windowshosting'
Version = '2.0.5'
Url = 'https://download.microsoft.com/download/1/1/0/11046135-4207-40D3-A795-13ECEA741B32/DotNetCore.2.0.5-WindowsHosting.exe'
Checksum = '98a577cfee15a521484972fc7b6f212ccc37141502b417fcb003b29e67af732b6018b01dbe7b3eca22dcad7ec4e6fbb4f01898a15ffcf8342d7f4f5712eaee1c'
ChecksumType = 'sha512'
Url64 = 'https://download.microsoft.com/download/1/1/0/11046135-4207-40D3-A795-13ECEA741B32/DotNetCore.2.0.5-WindowsHosting.exe'
Checksum64 = '98a577cfee15a521484972fc7b6f212ccc37141502b417fcb003b29e67af732b6018b01dbe7b3eca22dcad7ec4e6fbb4f01898a15ffcf8342d7f4f5712eaee1c'
ChecksumType64 = 'sha512'
ApplicationName = 'Microsoft .NET Core 2.0.5 - Windows Server Hosting'
UninstallerName = 'DotNetCore.2.0.5-WindowsHosting.exe'
AdditionalArgumentsToInstaller = 'OPT_INSTALL_LTS_REDIST=0 OPT_INSTALL_FTS_REDIST=0'
}
Log in or click on link to see number of positives.
- DotNetCore.2.0.5-WindowsHosting.exe (ef169c88fd8d) - ## / 67
- dotnetcore-windowshosting.2.0.5.20180111.nupkg (55f582c67d4a) - ## / 61
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.
.NET Foundation and Contributors
-
- chocolatey-core.extension (≥ 1.1.0)
- aspnetcore-runtimepackagestore (≥ 2.0.5)
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.