Downloads:
217,304
Downloads of v 15.0.25914.20161116-RC:
354
Last Update:
17 Nov 2016
Package Maintainer(s):
Software Author(s):
- Microsoft
Tags:
microsoft visual studio 2017 community ide visualstudio vs vs15- 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
Visual Studio 2017 Community - Release Candidate
This is a prerelease version of Visual Studio 2017 Community - Release Candidate.
- 1
- 2
- 3
15.0.25914.20161116-RC | Updated: 17 Nov 2016
- 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:
217,304
Downloads of v 15.0.25914.20161116-RC:
354
Maintainer(s):
Software Author(s):
- Microsoft
Visual Studio 2017 Community - Release Candidate 15.0.25914.20161116-RC
This is a prerelease version of Visual Studio 2017 Community - Release Candidate.
- 1
- 2
- 3
This Package Contains an Exempted Check
Not All Tests Have Passed
This package is unlisted and hidden from package listings.
Overview
Free, full-featured and extensible tool for students, open-source and individual developers.
Boosted productivity
Enhancements to code navigation, IntelliSense, refactoring, code fixes, and debugging, saves you time and effort on everyday tasks regardless of language or platform. In addition, for teams embracing DevOps, Visual Studio 2017 streamlines the developer inner loop and speeds up code flow with the brand new real time features such as live unit testing and real-time architectural dependency validation.
Redefined fundamentals
There is a renewed focus to enhance the efficiency of the fundamental tasks developers encounter on daily basis. From a brand-new lightweight and modular installation tailored to developers’ need, a faster IDE from startup to shut down, to a new way of view, edit, and debug any code without projects and solutions. Visual Studio 2017 helps developers stay focused on the big picture.
Streamlined Azure development
Built-in suite of Azure tools that enable developers to easily create cloud-first applications powered by Microsoft Azure. Visual Studio makes it easy to configure, build, debug, package, and deploy applications and services on Microsoft Azure directly from the IDE.
Five-star mobile development
With advanced debugging and profiling tools and unit test generation features, Visual Studio 2017 with Xamarin makes it faster and easier than ever for developers to build, connect, and tune mobile apps for Android, iOS, and Windows. Developer can also choose to develop mobile apps with Apache Cordova or Visual C++ cross platform library development in Visual Studio.
Customizations and Optional features
Not yet. Expect them in the final released version.
Installation notes
IMPORTANT: This release uses the new Visual Studio installer, which does not support unattended installation yet. Therefore, the installation of this page will require user interaction.
A reboot will most certainly be required after installing/uninstalling this package. A reboot might even be required before installing/uninstalling - if the system is awaiting a reboot due to Windows updates having been installed, or if you are attempting to uninstall the package immediately after installing it. The package will provide informative messages in each case.
If control over reboots is required, please install the dependencies (like dotnet4.6 or later) first, perform a reboot if needed, and then continue with the VS package install.
Uninstall-VS `
����-PackageName 'VisualStudio2017Community' `
����-ApplicationName 'Microsoft Visual Studio Community 2017' `
����-UninstallerName 'vs_installer.exe' `
����-AssumeNewVS2017Installer `
����-InstallerDisplayName 'Microsoft Visual Studio Installer'
# based on code from the visualstudio2015community/visualstudio2017enterprise package, with several extensions and modifications
# Parse input argument string into a hashtable
# Format: --AdminFile file location --Features WebTools,Win8SDK --ProductKey AB-D1
function Parse-Parameters
{
[CmdletBinding()]
Param (
[string] $s
)
Write-Debug "Running 'Parse-Parameters' with s:'$s'";
$parameters = @{ }
if ($s -eq '')
{
Write-Debug "No package parameters."
return $parameters
}
Write-Debug "Package parameters: $s"
$s = ' ' + $s
[String[]] $kvpPrefix = @(" --")
$kvpDelimiter = ' '
$kvps = $s.Split($kvpPrefix, [System.StringSplitOptions]::RemoveEmptyEntries)
foreach ($kvp in $kvps)
{
Write-Debug "Package parameter kvp: $kvp"
$delimiterIndex = $kvp.IndexOf($kvpDelimiter)
if (($delimiterIndex -le 0) -or ($delimiterIndex -ge ($kvp.Length - 1))) { continue }
$key = $kvp.Substring(0, $delimiterIndex).Trim().ToLower()
if ($key -eq '') { continue }
$value = $kvp.Substring($delimiterIndex + 1).Trim()
Write-Debug "Package parameter: key=$key, value=$value"
$parameters.Add($key, $value)
}
return $parameters
}
# Generates customizations file. Returns its path
function Generate-AdminFile
{
[CmdletBinding()]
Param (
[Parameter(Mandatory = $true)]
[hashtable] $parameters,
[string] $adminFile,
[Parameter(Mandatory = $true)]
[string] $packageName
)
Write-Debug "Running 'Generate-AdminFile' with parameters:'$parameters', defaultAdminFile:'$defaultAdminFile', packageName:'$packageName'";
$adminFile = $parameters['AdminFile']
$features = $parameters['Features']
if ($adminFile -eq '' -and !$features)
{
return $null
}
$localAdminFile = Join-Path $Env:TEMP "${packageName}_AdminDeployment.xml"
if (Test-Path $localAdminFile)
{
Remove-Item $localAdminFile
}
if ($adminFile)
{
if (Test-Path $adminFile)
{
Copy-Item $adminFile $localAdminFile -force
}
else
{
if (($adminFile -as [System.URI]).AbsoluteURI -ne $null)
{
Get-ChocolateyWebFile 'adminFile' $localAdminFile $adminFile
}
else
{
throw 'Invalid AdminFile setting.'
}
}
Write-Verbose "Using provided AdminFile: $adminFile"
}
elseif ($features)
{
Copy-Item $defaultAdminFile $localAdminFile -force
}
return $localAdminFile
}
# Turns on features in the customizations file
function Update-AdminFile
{
[CmdletBinding()]
Param (
[Parameter(Mandatory = $true)]
[hashtable] $parameters,
[string] $adminFile
)
Write-Debug "Running 'Update-AdminFile' with parameters:'$parameters', adminFile:'$adminFile'";
if ($adminFile -eq '') { return }
$s = $parameters['Features']
if (!$s) { return }
$features = $s.Split(',')
[xml]$xml = Get-Content $adminFile
$selectableItemCustomizations = $xml.DocumentElement.SelectableItemCustomizations
$featuresSelectedByDefault = $selectableItemCustomizations.ChildNodes | Where-Object { $_.GetAttribute('Hidden') -eq 'no' -and $_.GetAttribute('Selected') -eq 'yes' } | Select-Object -ExpandProperty Id
$selectedFeatures = New-Object System.Collections.ArrayList
$invalidFeatures = New-Object System.Collections.ArrayList
foreach ($feature in $features)
{
$node = $selectableItemCustomizations.SelectSingleNode("*[@Id=""$feature""]")
if ($node -ne $null)
{
$node.Selected = "yes"
$selectedFeatures.Add($feature) | Out-Null
}
else
{
$invalidFeatures.Add($feature) | Out-Null
}
}
if ($invalidFeatures.Count -gt 0)
{
$errorMessage = "Invalid feature name(s): $invalidFeatures"
$validFeatureNames = $selectableItemCustomizations.ChildNodes | Select-Object -ExpandProperty Id
Write-Warning $errorMessage
Write-Warning "Valid feature names are: $validFeatureNames"
throw $errorMessage
}
Write-Verbose "Features selected by default: $featuresSelectedByDefault"
Write-Verbose "Features selected using package parameters: $selectedFeatures"
$xml.Save($adminFile)
}
function Generate-InstallArgumentsString
{
[CmdletBinding()]
Param (
[Parameter(Mandatory = $true)]
[hashtable] $parameters,
[string] $adminFile,
[Parameter(Mandatory = $true)]
[string] $logFilePath,
[switch] $assumeNewVS2017Installer
)
Write-Debug "Running 'Generate-InstallArgumentsString' with parameters:'$parameters', adminFile:'$adminFile', logFilePath:'$logFilePath', assumeNewVS2017Installer:'$assumeNewVS2017Installer'";
if ($assumeNewVS2017Installer)
{
Write-Warning "The new VS2017 installer does not support setting the path to the log file yet."
$s = ''
if ($adminFile -ne '')
{
Write-Warning "The new VS2017 installer does not support an admin file yet."
}
Write-Warning "The new VS2017 installer does not support silent installation yet."
}
else
{
$s = "/Passive /NoRestart /Log ""$logFilePath"""
if ($adminFile -ne '')
{
$s = $s + " /AdminFile $adminFile"
}
}
$pk = $parameters['ProductKey']
if ($pk -and (-not [string]::IsNullOrEmpty($pk)))
{
if ($assumeNewVS2017Installer)
{
Write-Warning "The new VS2017 installer does not support providing a product key yet."
}
else
{
Write-Verbose "Using provided product key: ...-$($pk.Substring([Math]::Max($pk.Length - 5, 0)))"
$s = $s + " /ProductKey $pk"
}
}
return $s
}
function Generate-UninstallArgumentsString
{
[CmdletBinding()]
Param (
[Parameter(Mandatory = $true)]
[string] $logFilePath,
[switch] $assumeNewVS2017Installer
)
Write-Debug "Running 'Generate-UninstallArgumentsString' with logFilePath:'$logFilePath', assumeNewVS2017Installer:'$assumeNewVS2017Installer'";
if ($assumeNewVS2017Installer)
{
Write-Warning "The new VS2017 installer does not support setting the path to the log file yet."
$s = "/uninstall"
Write-Warning "The new VS2017 installer does not support silent uninstallation yet."
}
else
{
$s = "/Uninstall /Force /Passive /NoRestart /Log ""$logFilePath"""
}
return $s
}
function Get-VSUninstallRegistryKey
{
[CmdletBinding()]
Param (
[string] $ApplicationName
)
Write-Debug "Looking for Uninstall key for '$ApplicationName'"
$uninstallKey = @('Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall', 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall') `
| Where-Object { Test-Path -Path $_ } `
| Get-ChildItem `
| Where-Object { $displayName = $_ | Get-ItemProperty -Name DisplayName -ErrorAction SilentlyContinue | Select-Object -ExpandProperty DisplayName; $displayName -eq $ApplicationName } `
| Where-Object { $systemComponent = $_ | Get-ItemProperty -Name SystemComponent -ErrorAction SilentlyContinue | Select-Object -ExpandProperty SystemComponent; $systemComponent -ne 1 }
return $uninstallKey
}
if (-not (Test-Path -Path Function:\Set-PowerShellExitCode))
{
# based on Set-PowerShellExitCode (07277ac), included here unchanged to add exit code support to old Chocolatey
function Set-PowerShellExitCode {
param (
[int]$exitCode
)
$host.SetShouldExit($exitCode);
$env:ChocolateyExitCode = $exitCode;
}
}
# based on Start-ChocolateyProcessAsAdmin (8734611), included here only slightly modified (renamed, stricter parameter binding), to add exit code support to old Chocolatey
function Start-VSChocolateyProcessAsAdmin {
[CmdletBinding()]
param(
[string] $statements,
[string] $exeToRun = 'powershell',
[switch] $minimized,
[switch] $noSleep,
[int[]]$validExitCodes = @(0)
)
Write-Debug "Running 'Start-VSChocolateyProcessAsAdmin' with exeToRun:'$exeToRun', statements:'$statements', minimized:$minimized, noSleep:$noSleep, validExitCodes:'$validExitCodes'";
$wrappedStatements = $statements
if ($wrappedStatements -eq $null) { $wrappedStatements = ''}
if ($exeToRun -eq 'powershell') {
$exeToRun = "$($env:SystemRoot)\System32\WindowsPowerShell\v1.0\powershell.exe"
$importChocolateyHelpers = ""
Get-ChildItem "$helpersPath" -Filter *.psm1 | ForEach-Object { $importChocolateyHelpers = "& import-module -name `'$($_.FullName)`';$importChocolateyHelpers" };
$block = @"
`$noSleep = `$$noSleep
$importChocolateyHelpers
try{
`$progressPreference="SilentlyContinue"
$statements
if(!`$noSleep){start-sleep 6}
}
catch{
if(!`$noSleep){start-sleep 8}
throw
}
"@
$encoded = [Convert]::ToBase64String([System.Text.Encoding]::Unicode.GetBytes($block))
$wrappedStatements = "-NoProfile -ExecutionPolicy bypass -EncodedCommand $encoded"
$dbgMessage = @"
Elevating Permissions and running powershell block:
$block
This may take a while, depending on the statements.
"@
}
else
{
$dbgMessage = @"
Elevating Permissions and running [`"$exeToRun`" $wrappedStatements]. This may take a while, depending on the statements.
"@
}
Write-Debug $dbgMessage
$exeIsTextFile = [System.IO.Path]::GetFullPath($exeToRun) + ".istext"
if (([System.IO.File]::Exists($exeIsTextFile))) {
Set-PowerShellExitCode 4
throw "The file was a text file but is attempting to be run as an executable - '$exeToRun'"
}
if ($exeToRun -eq 'msiexec' -or $exeToRun -eq 'msiexec.exe') {
$exeToRun = "$($env:SystemRoot)\System32\msiexec.exe"
}
if (!([System.IO.File]::Exists($exeToRun)) -and $exeToRun -notmatch 'msiexec') {
Write-Warning "May not be able to find '$exeToRun'. Please use full path for executables."
# until we have search paths enabled, let's just pass a warning
#Set-PowerShellExitCode 2
#throw "Could not find '$exeToRun'"
}
# Redirecting output slows things down a bit.
$writeOutput = {
if ($EventArgs.Data -ne $null) {
Write-Host "$($EventArgs.Data)"
}
}
$writeError = {
if ($EventArgs.Data -ne $null) {
Write-Error "$($EventArgs.Data)"
}
}
$process = New-Object System.Diagnostics.Process
$process.EnableRaisingEvents = $true
Register-ObjectEvent -InputObject $process -SourceIdentifier "LogOutput_ChocolateyProc" -EventName OutputDataReceived -Action $writeOutput | Out-Null
Register-ObjectEvent -InputObject $process -SourceIdentifier "LogErrors_ChocolateyProc" -EventName ErrorDataReceived -Action $writeError | Out-Null
#$process.StartInfo = New-Object System.Diagnostics.ProcessStartInfo($exeToRun, $wrappedStatements)
# in case empty args makes a difference, try to be compatible with the older
# version
$psi = New-Object System.Diagnostics.ProcessStartInfo
$psi.FileName = $exeToRun
if ($wrappedStatements -ne '') {
$psi.Arguments = "$wrappedStatements"
}
$process.StartInfo = $psi
# process start info
$process.StartInfo.RedirectStandardOutput = $true
$process.StartInfo.RedirectStandardError = $true
$process.StartInfo.UseShellExecute = $false
$process.StartInfo.WorkingDirectory = Get-Location
if ([Environment]::OSVersion.Version -ge (New-Object 'Version' 6,0)){
Write-Debug "Setting RunAs for elevation"
$process.StartInfo.Verb = "RunAs"
}
if ($minimized) {
$process.StartInfo.WindowStyle = [System.Diagnostics.ProcessWindowStyle]::Minimized
}
$process.Start() | Out-Null
if ($process.StartInfo.RedirectStandardOutput) { $process.BeginOutputReadLine() }
if ($process.StartInfo.RedirectStandardError) { $process.BeginErrorReadLine() }
$process.WaitForExit()
# For some reason this forces the jobs to finish and waits for
# them to do so. Without this it never finishes.
Unregister-Event -SourceIdentifier "LogOutput_ChocolateyProc"
Unregister-Event -SourceIdentifier "LogErrors_ChocolateyProc"
$exitCode = $process.ExitCode
$process.Dispose()
Write-Debug "Command [`"$exeToRun`" $wrappedStatements] exited with `'$exitCode`'."
if ($validExitCodes -notcontains $exitCode) {
Set-PowerShellExitCode $exitCode
throw "Running [`"$exeToRun`" $statements] was not successful. Exit code was '$exitCode'. See log for possible error messages."
}
Write-Debug "Finishing 'Start-VSChocolateyProcessAsAdmin'"
return $exitCode
}
# based on Install-ChocolateyPackage (a9519b5), with changes:
# - added recognition of exit codes signifying reboot requirement
# - VS installers are exe
# - local file name is extracted from the url (to avoid passing -getOriginalFileName to Get-ChocolateyWebFile for compatibility with old Chocolatey)
# - removed Get-ChocolateyWebFile options support (for compatibility with old Chocolatey)
# - removed exit code parameters in order to centralize exit code logic
function Install-VSChocolateyPackage
{
[CmdletBinding()]
param(
[string] $packageName,
[string] $silentArgs = '',
[string] $url,
[alias("url64")][string] $url64bit = '',
[string] $checksum = '',
[string] $checksumType = '',
[string] $checksum64 = '',
[string] $checksumType64 = '',
[string] $logFilePath,
[switch] $assumeNewVS2017Installer
)
Write-Debug "Running 'Install-VSChocolateyPackage' for $packageName with url:'$url', args:'$silentArgs', url64bit:'$url64bit', checksum:'$checksum', checksumType:'$checksumType', checksum64:'$checksum64', checksumType64:'$checksumType64', logFilePath:'$logFilePath'";
$chocTempDir = $env:TEMP
$tempDir = Join-Path $chocTempDir "$packageName"
if ($env:packageVersion -ne $null) { $tempDir = Join-Path $tempDir "$env:packageVersion" }
if (![System.IO.Directory]::Exists($tempDir)) { [System.IO.Directory]::CreateDirectory($tempDir) | Out-Null }
$urlForFileNameDetermination = $url
if ($urlForFileNameDetermination -eq '') { $urlForFileNameDetermination = $url64bit }
if ($urlForFileNameDetermination -like '*.exe') { $localFileName = $urlForFileNameDetermination.Substring($urlForFileNameDetermination.LastIndexOfAny(@('/', '\')) + 1) }
else { $localFileName = 'vs_setup.exe' }
$localFilePath = Join-Path $tempDir $localFileName
$arguments = @{
packageName = $packageName
fileFullPath = $localFilePath
url = $url
url64bit = $url64bit
checksum = $checksum
checksumType = $checksumType
checksum64 = $checksum64
checksumType64 = $checksumType64
}
Get-ChocolateyWebFile @arguments | Out-Null
$arguments = @{
packageName = $packageName
silentArgs = $silentArgs
file = $localFilePath
logFilePath = $logFilePath
assumeNewVS2017Installer = $assumeNewVS2017Installer
}
Install-VSChocolateyInstallPackage @arguments
}
# based on Install-ChocolateyInstallPackage (fbe24a8), with changes:
# - added recognition of exit codes signifying reboot requirement
# - VS installers are exe
# - dropped support for chocolateyInstallArguments and chocolateyInstallOverride
# - removed unreferenced parameter
# - refactored logic shared with Uninstall-VSChocolateyPackage to a generic function
# - removed exit code parameters in order to centralize exit code logic
function Install-VSChocolateyInstallPackage {
[CmdletBinding()]
param(
[string] $packageName,
[string] $silentArgs = '',
[string] $file,
[string] $logFilePath,
[switch] $assumeNewVS2017Installer
)
Write-Debug "Running 'Install-VSChocolateyInstallPackage' for $packageName with file:'$file', silentArgs:'$silentArgs', logFilePath:'$logFilePath', assumeNewVS2017Installer:'$assumeNewVS2017Installer'"
$installMessage = "Installing $packageName..."
Write-Host $installMessage
if ($file -eq '' -or $file -eq $null) {
throw 'Package parameters incorrect, File cannot be empty.'
}
Start-VSServicingOperation @PSBoundParameters -operationTexts @('installed', 'installing', 'installation')
}
# based on Uninstall-ChocolateyPackage (01db65b), with changes:
# - added recognition of exit codes signifying reboot requirement
# - VS installers are exe
# - dropped support for chocolateyInstallArguments and chocolateyInstallOverride
# - refactored logic shared with Install-VSChocolateyInstallPackage to a generic function
# - removed exit code parameters in order to centralize exit code logic
function Uninstall-VSChocolateyPackage
{
[CmdletBinding()]
param(
[string] $packageName,
[string] $silentArgs = '',
[string] $file
)
Write-Debug "Running 'Uninstall-VSChocolateyPackage' for $packageName with silentArgs:'$silentArgs', file:'$file'"
$installMessage = "Uninstalling $packageName..."
Write-Host $installMessage
Start-VSServicingOperation @PSBoundParameters -operationTexts @('uninstalled', 'uninstalling', 'uninstallation')
}
function Start-VSServicingOperation
{
[CmdletBinding()]
param(
[string] $packageName,
[string] $silentArgs,
[string] $file,
[string] $logFilePath,
[string[]] $operationTexts,
[switch] $assumeNewVS2017Installer
)
Write-Debug "Running 'Start-VSServicingOperation' for $packageName with silentArgs:'$silentArgs', file:'$file', logFilePath:$logFilePath', operationTexts:'$operationTexts', assumeNewVS2017Installer:'$assumeNewVS2017Installer'"
$frobbed, $frobbing, $frobbage = $operationTexts
$successExitCodes = @(
0 # success
)
$rebootExitCodes = @(
3010 # success, restart required
)
$priorRebootRequiredExitCodes = @(
-2147185721 # Restart is required before (un)installation can continue
)
$blockExitCodes = @(
-2147205120, # block, restart not required
-2147172352 # block, restart required
)
$validExitCodes = @()
if (($successExitCodes | Measure-Object).Count -gt 0) { $validExitCodes += $successExitCodes }
if (($rebootExitCodes | Measure-Object).Count -gt 0) { $validExitCodes += $rebootExitCodes }
if (($priorRebootRequiredExitCodes | Measure-Object).Count -gt 0) { $validExitCodes += $priorRebootRequiredExitCodes }
if (($blockExitCodes | Measure-Object).Count -gt 0) { $validExitCodes += $blockExitCodes }
$exitCode = Start-VSChocolateyProcessAsAdmin -statements $silentArgs -exeToRun $file -validExitCodes $validExitCodes
if ($assumeNewVS2017Installer)
{
Write-Debug 'Looking for vs_installer.exe processes spawned by the bootstrapper'
$installerProcesses = Get-Process -Name 'vs_installer' -ErrorAction SilentlyContinue
$installerProcessesCount = ($installerProcesses | Measure-Object).Count
if ($installerProcessesCount -gt 0)
{
Write-Debug "Found $installerProcessesCount vs_installer.exe process(es): $($installerProcesses | Select-Object -ExpandProperty Id)"
Write-Debug "Waiting for all vs_installer.exe processes to exit"
$installerProcesses | Wait-Process
foreach ($proc in $installerProcesses)
{
if ($proc.ExitCode -ne 0)
{
Write-Warning "vs_installer.exe process $($proc.Id) exited with code $($proc.ExitCode)"
if ($exitCode -eq 0)
{
$exitCode = $proc.ExitCode
}
}
else
{
Write-Debug "vs_installer.exe process $($proc.Id) exited with code $($proc.ExitCode)"
}
}
}
else
{
Write-Debug 'Did not find any running vs_installer.exe processes.'
}
}
$Env:ChocolateyExitCode = $exitCode
$warnings = @()
if (($blockExitCodes | Measure-Object).Count -gt 0 -and $blockExitCodes -contains $exitCode)
{
$exceptionMessage = "${packageName} cannot be ${frobbed} on this system."
$success = $false
if ($logFilePath -ne '' -and (Test-Path -Path $logFilePath))
{
# [0C40:07D8][2016-05-28T23:17:32]i000: MUX: Stop Block: MinimumOSLevel : This version of Visual Studio requires a computer with a !$!http://go.microsoft.com/fwlink/?LinkID=647155&clcid=0x409!,!newer version of Windows!@!.
# [0C40:07D8][2016-05-28T23:17:32]i000: MUX: Stop Block: SystemRebootPendingBlock : The computer needs to be restarted before setup can continue. Please restart the computer and run setup again.
$blocks = Get-Content -Path $logFilePath `
| Select-String '(?<=Stop Block: ).+$' `
| Select-Object -ExpandProperty Matches `
| Where-Object { $_.Success -eq $true } `
| Select-Object -ExpandProperty Value `
| Sort-Object -Unique
if (($blocks | Measure-Object).Count -gt 0)
{
$warnings = @("${packageName} cannot be ${frobbed} due to the following issues:") + $blocks
$exceptionMessage += " You may attempt to fix the issues listed and try again."
}
}
}
elseif (($priorRebootRequiredExitCodes | Measure-Object).Count -gt 0 -and $priorRebootRequiredExitCodes -contains $exitCode)
{
$exceptionMessage = "The computer must be rebooted before ${frobbing} ${packageName}. Please reboot the computer and run the ${frobbage} again."
$success = $false
}
elseif (($rebootExitCodes | Measure-Object).Count -gt 0 -and $rebootExitCodes -contains $exitCode)
{
$needsReboot = $true
$success = $true
}
else
{
$needsReboot = $false
$success = $true
}
if ($success)
{
if ($needsReboot)
{
Write-Warning "${packageName} has been ${frobbed}. However, a reboot is required to finalize the ${frobbage}."
}
else
{
Write-Host "${packageName} has been ${frobbed}."
}
}
else
{
if ($warnings -ne $null)
{
$warnings | Write-Warning
}
throw $exceptionMessage
}
}
function Install-VS {
<#
.SYNOPSIS
Installs Visual Studio
.DESCRIPTION
Installs Visual Studio with ability to specify additional features and supply product key.
.PARAMETER PackageName
The name of the VisualStudio package - this is arbitrary.
It's recommended you call it the same as your nuget package id.
.PARAMETER Url
This is the url to download the VS web installer.
.PARAMETER ChecksumSha1
The SHA-1 hash of the VS web installer file.
.EXAMPLE
Install-VS -PackageName VisualStudio2017Community -Url 'http://download.microsoft.com/download/zzz/vs_community.exe' -ChecksumSha1 'ABCDEF0123456789ABCDEF0123456789ABCDEF12'
.OUTPUTS
None
.NOTES
This helper reduces the number of lines one would have to write to download and install Visual Studio.
This method has no error handling built into it.
.LINK
Install-ChocolateyPackage
#>
[CmdletBinding()]
param(
[string] $PackageName,
[string] $ApplicationName,
[string] $Url,
[string] $ChecksumSha1,
[switch] $AssumeNewVS2017Installer,
[string] $InstallerDisplayName = $ApplicationName
)
if ($Env:ChocolateyPackageDebug -ne $null)
{
$VerbosePreference = 'Continue'
$DebugPreference = 'Continue'
Write-Warning "VerbosePreference and DebugPreference set to Continue due to the presence of ChocolateyPackageDebug environment variable"
}
Write-Debug "Running 'Install-VS' for $PackageName with Url:'$Url' ChecksumSha1:$ChecksumSha1";
$uninstallKey = Get-VSUninstallRegistryKey -ApplicationName $InstallerDisplayName
$count = ($uninstallKey | Measure-Object).Count
if ($count -gt 0)
{
if ($AssumeNewVS2017Installer)
{
Write-Warning "$ApplicationName is already installed. Please use $InstallerDisplayName in the Start Menu to modify or repair it."
}
else
{
Write-Warning "$ApplicationName is already installed. Please use Programs and Features in the Control Panel to modify or repair it."
}
return
}
$packageParameters = Parse-Parameters $env:chocolateyPackageParameters
if ($packageParameters.Length -gt 0) { Write-Debug $packageParameters }
if ($AssumeNewVS2017Installer)
{
$adminFile = $null
}
else
{
$defaultAdminFile = (Join-Path $PSScriptRoot 'AdminDeployment.xml')
Write-Debug "Default AdminFile: $defaultAdminFile"
$adminFile = Generate-AdminFile $packageParameters $defaultAdminFile $PackageName
Write-Debug "AdminFile: $adminFile"
Update-AdminFile $packageParameters $adminFile
}
$logFilePath = Join-Path $Env:TEMP "${PackageName}.log"
Write-Debug "Log file path: $logFilePath"
$silentArgs = Generate-InstallArgumentsString -parameters $packageParameters -adminFile $adminFile -logFilePath $logFilePath -assumeNewVS2017Installer:$AssumeNewVS2017Installer
$arguments = @{
packageName = $PackageName
silentArgs = $silentArgs
url = $Url
checksum = $ChecksumSha1
checksumType = 'sha1'
logFilePath = $logFilePath
assumeNewVS2017Installer = $AssumeNewVS2017Installer
}
$argumentsDump = ($arguments.GetEnumerator() | % { '-{0}:''{1}''' -f $_.Key,"$($_.Value)" }) -join ' '
Write-Debug "Install-VSChocolateyPackage $argumentsDump"
Install-VSChocolateyPackage @arguments
}
function Uninstall-VS {
<#
.SYNOPSIS
Uninstalls Visual Studio
.DESCRIPTION
Uninstalls Visual Studio.
.PARAMETER PackageName
The name of the VisualStudio package.
.PARAMETER ApplicationName
The VisualStudio app name - i.e. 'Microsoft Visual Studio Community 2017'.
.PARAMETER UninstallerName
This name of the installer executable - i.e. 'vs_community.exe'.
.EXAMPLE
Uninstall-VS 'VisualStudio2017Community' 'Microsoft Visual Studio Community 2017' 'vs_community.exe'
.OUTPUTS
None
.NOTES
This helper reduces the number of lines one would have to write to uninstall Visual Studio.
This method has no error handling built into it.
.LINK
Uninstall-ChocolateyPackage
#>
[CmdletBinding()]
param(
[string] $PackageName,
[string] $ApplicationName,
[string] $UninstallerName,
[switch] $AssumeNewVS2017Installer,
[string] $InstallerDisplayName = $ApplicationName
)
if ($Env:ChocolateyPackageDebug -ne $null)
{
$VerbosePreference = 'Continue'
$DebugPreference = 'Continue'
Write-Warning "VerbosePreference and DebugPreference set to Continue due to the presence of ChocolateyPackageDebug environment variable"
}
Write-Debug "Running 'Uninstall-VS' for $PackageName with ApplicationName:'$ApplicationName' UninstallerName:'$UninstallerName' AssumeNewVS2017Installer:'$AssumeNewVS2017Installer' InstallerDisplayName:'$InstallerDisplayName'";
$informMaintainer = "Please report this to the maintainer of this package ($PackageName)."
$uninstallKey = Get-VSUninstallRegistryKey -ApplicationName $InstallerDisplayName
$count = ($uninstallKey | Measure-Object).Count
Write-Debug "Found $count Uninstall key(s)"
if ($count -eq 0)
{
Write-Warning "Uninstall information for $InstallerDisplayName 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 $InstallerDisplayName! $informMaintainer"
}
Write-Debug "Using Uninstall key: $($uninstallKey.PSPath)"
$uninstallString = $uninstallKey | Get-ItemProperty -Name UninstallString | Select-Object -ExpandProperty UninstallString
Write-Debug "UninstallString: $uninstallString"
if ($AssumeNewVS2017Installer)
{
# C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe /uninstall
$uninstallerExePathRegexString = '^(.+[^\s])\s/uninstall$'
}
else
{
# "C:\ProgramData\Package Cache\{4f075c79-8ee3-4c85-9408-828736d1f7f3}\vs_community.exe" /uninstall
$uninstallerExePathRegexString = '^\s*(\"[^\"]+\")|([^\s]+)'
}
if (-not ($uninstallString -match $uninstallerExePathRegexString))
{
throw "UninstallString '$uninstallString' is not of the expected format. $informMaintainer"
}
$uninstallerPath = $matches[1].Trim('"')
Write-Debug "uninstallerPath: $uninstallerPath"
if ((Split-Path -Path $uninstallerPath -Leaf) -ne $UninstallerName)
{
throw "The uninstaller file name is unexpected (uninstallerPath: $uninstallerPath). $informMaintainer"
}
$logFilePath = Join-Path $Env:TEMP "${PackageName}_uninstall.log"
Write-Debug "Log file path: $logFilePath"
$silentArgs = Generate-UninstallArgumentsString -logFilePath $logFilePath -assumeNewVS2017Installer:$AssumeNewVS2017Installer
$arguments = @{
packageName = $PackageName
silentArgs = $silentArgs
file = $uninstallerPath
}
$argumentsDump = ($arguments.GetEnumerator() | % { '-{0}:''{1}''' -f $_.Key,"$($_.Value)" }) -join ' '
Write-Debug "Uninstall-VSChocolateyPackage $argumentsDump"
Uninstall-VSChocolateyPackage @arguments
}
Export-ModuleMember Install-VS, Uninstall-VS
Log in or click on link to see number of positives.
- VisualStudio2017Community.15.0.25914.20161116-RC.nupkg (d134e56edf39) - ## / 56
- vs_Community.exe (448af03f25fe) - ## / 56
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 |
---|---|---|---|---|
Visual Studio 2017 Community 15.9.60.0 | 1640 | Thursday, February 15, 2024 | Approved | |
Visual Studio 2017 Community 15.9.59.0 | 1283 | Wednesday, January 10, 2024 | Approved | |
Visual Studio 2017 Community 15.9.58.0 | 2170 | Sunday, October 15, 2023 | Approved | |
Visual Studio 2017 Community 15.9.57.0 | 693 | Saturday, September 23, 2023 | Approved | |
Visual Studio 2017 Community 15.9.56.0 | 482 | Tuesday, September 5, 2023 | Approved | |
Visual Studio 2017 Community 15.9.55.0 | 2219 | Sunday, June 18, 2023 | Approved | |
Visual Studio 2017 Community 15.9.54.0 | 2309 | Friday, April 21, 2023 | Approved | |
Visual Studio 2017 Community 15.9.53.0 | 2087 | Friday, March 17, 2023 | Approved | |
Visual Studio 2017 Community 15.9.52.0 | 1531 | Thursday, February 23, 2023 | Approved | |
Visual Studio 2017 Community 15.9.51.0 | 4444 | Wednesday, November 16, 2022 | Approved | |
Visual Studio 2017 Community 15.9.50.0 | 3190 | Saturday, August 27, 2022 | Approved | |
Visual Studio 2017 Community 15.9.49.0 | 6182 | Monday, June 20, 2022 | Approved | |
Visual Studio 2017 Community 15.9.48.0 | 5445 | Tuesday, May 17, 2022 | Approved | |
Visual Studio 2017 Community 15.9.47.0 | 3694 | Wednesday, April 20, 2022 | Approved | |
Visual Studio 2017 Community 15.9.46.0 | 340 | Tuesday, April 19, 2022 | Approved | |
Visual Studio 2017 Community 15.9.45.0 | 3728 | Saturday, March 12, 2022 | Approved | |
Visual Studio 2017 Community 15.9.44.0 | 2924 | Thursday, February 10, 2022 | Approved | |
Visual Studio 2017 Community 15.9.43.0 | 1618 | Wednesday, January 12, 2022 | Approved | |
Visual Studio 2017 Community 15.9.42.0 | 6998 | Thursday, December 16, 2021 | Approved | |
Visual Studio 2017 Community 15.9.41.0 | 1678 | Friday, November 12, 2021 | Approved | |
Visual Studio 2017 Community 15.9.40.0 | 1888 | Saturday, October 16, 2021 | Approved | |
Visual Studio 2017 Community 15.9.39.0 | 1618 | Wednesday, September 15, 2021 | Approved | |
Visual Studio 2017 Community 15.9.38.0 | 1745 | Sunday, August 22, 2021 | Approved | |
Visual Studio 2017 Community 15.9.37.0 | 3010 | Thursday, July 22, 2021 | Approved | |
Visual Studio 2017 Community 15.9.36.0 | 14783 | Sunday, May 16, 2021 | Approved | |
Visual Studio 2017 Community 15.9.35.0 | 2669 | Saturday, April 17, 2021 | Approved | |
Visual Studio 2017 Community 15.9.34.0 | 2337 | Wednesday, March 10, 2021 | Approved | |
Visual Studio 2017 Community 15.9.33.0 | 3300 | Sunday, February 14, 2021 | Approved | |
Visual Studio 2017 Community 15.9.31.0 | 2232 | Wednesday, January 13, 2021 | Approved | |
Visual Studio 2017 Community 15.9.30.0 | 2243 | Wednesday, December 9, 2020 | Approved | |
Visual Studio 2017 Community 15.9.29.0 | 1829 | Tuesday, November 10, 2020 | Approved | |
Visual Studio 2017 Community 15.9.28.0 | 1856 | Sunday, October 18, 2020 | Approved | |
Visual Studio 2017 Community 15.9.27.0 | 2171 | Friday, September 11, 2020 | Approved | |
Visual Studio 2017 Community 15.9.26.0 | 1901 | Monday, August 24, 2020 | Approved | |
Visual Studio 2017 Community 15.9.25.0 | 2346 | Friday, July 24, 2020 | Approved | |
Visual Studio 2017 Community 15.9.23.0 | 5009 | Friday, May 15, 2020 | Approved | |
Visual Studio 2017 Community 15.9.22.0 | 2477 | Wednesday, April 15, 2020 | Approved | |
Visual Studio 2017 Community 15.9.21.0 | 2746 | Wednesday, March 11, 2020 | Approved | |
Visual Studio 2017 Community 15.9.20.0 | 2598 | Wednesday, February 12, 2020 | Approved | |
Visual Studio 2017 Community 15.9.19.0 | 1504 | Sunday, February 2, 2020 | Approved | |
Visual Studio 2017 Community 15.9.18.0 | 7546 | Wednesday, December 11, 2019 | Approved | |
Visual Studio 2017 Community 15.9.17.0 | 5731 | Wednesday, October 16, 2019 | Approved | |
Visual Studio 2017 Community 15.9.16.0 | 3755 | Monday, September 16, 2019 | Approved | |
Visual Studio 2017 Community 15.9.15.0 | 3790 | Tuesday, August 20, 2019 | Approved | |
Visual Studio 2017 Community 15.9.11.0 | 19773 | Wednesday, April 10, 2019 | Approved | |
Visual Studio 2017 Community 15.9.10.0 | 5186 | Sunday, March 31, 2019 | Approved | |
Visual Studio 2017 Community 15.9.8.0 | 4057 | Saturday, March 9, 2019 | Approved | |
Visual Studio 2017 Community 15.9.7.0 | 2877 | Thursday, February 21, 2019 | Approved | |
Visual Studio 2017 Community 15.9.4.0 | 7329 | Saturday, January 5, 2019 | Approved | |
Visual Studio 2017 Community 15.9.2.0 | 4162 | Tuesday, November 27, 2018 | Approved | |
Visual Studio 2017 Community 15.9.1.0 | 2057 | Saturday, November 17, 2018 | Approved | |
Visual Studio 2017 Community 15.8.9.0 | 1790 | Wednesday, November 7, 2018 | Approved | |
Visual Studio 2017 Community 15.8.7.0 | 2378 | Wednesday, October 17, 2018 | Approved | |
Visual Studio 2017 Community 15.8.6.0 | 1987 | Tuesday, October 2, 2018 | Approved | |
Visual Studio 2017 Community 15.8.2.0 | 3946 | Monday, September 3, 2018 | Approved | |
Visual Studio 2017 Community 15.8.0.0 | 1942 | Thursday, August 16, 2018 | Approved |
-
- KB3033929 (≥ 1.0.0)
- KB2919355 (≥ 1.0.20160915)
- vcredist2012 (≥ 11.0.60610)
- vcredist2015 (≥ 14.0.24215.20160928)
- dotnet4.6.1 (≥ 4.6.1055.1)
Ground Rules:
- This discussion is only about Visual Studio 2017 Community - Release Candidate and the Visual Studio 2017 Community - Release Candidate 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 Visual Studio 2017 Community - Release Candidate, 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.