Downloads of v 3.0.569:


Last Update:

23 Jul 2018

Package Maintainer(s):

Software Author(s):

  • Microsoft


visualstudio2017 powershell tools vsix admin

PowerShell Tools for Visual Studio 2017

  • 1
  • 2
  • 3

3.0.569 | Updated: 23 Jul 2018



Downloads of v 3.0.569:



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
PowerShell Tools for Visual Studio 2017 3.0.569

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Exemption:

Package requires Visual Studio 2017 so will need an exemption.


Scan Testing Successful:

No detections found in any package files


To install PowerShell Tools for Visual Studio 2017, run the following command from the command line or from PowerShell:


To upgrade PowerShell Tools for Visual Studio 2017, run the following command from the command line or from PowerShell:


To uninstall PowerShell Tools for Visual Studio 2017, 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 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

4. Choose your deployment method:

choco upgrade visualstudio2017-powershelltools -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 visualstudio2017-powershelltools -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure visualstudio2017-powershelltools installed
    name: visualstudio2017-powershelltools
    state: present
    version: 3.0.569
    source: STEP 3 URL

See docs at

chocolatey_package 'visualstudio2017-powershelltools' do
  action    :install
  version  '3.0.569'
  source   'STEP 3 URL'

See docs at

    Name: visualstudio2017-powershelltools,
    Version: 3.0.569,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller visualstudio2017-powershelltools
   Name     = 'visualstudio2017-powershelltools'
   Ensure   = 'Present'
   Version  = '3.0.569'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'visualstudio2017-powershelltools':
  provider => 'chocolatey',
  ensure   => '3.0.569',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install visualstudio2017-powershelltools version="3.0.569" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator gep13 on 24 Jul 2018.


PowerShell Tools for Visual Studio - PowerShell editing and debugging in Visual Studio.


  • Microsoft Visual Studio 2017
  • PowerShell v3 or later


PowerShell Tools for Visual Studio brings the richness of the Visual Studio development experience together with the power of PowerShell. Using this extension you can:

  • Edit, run and debug PowerShell scripts locally and remotely using the Visual Studio debugger
  • Create projects for PowerShell scripts and modules
  • Leverage Visual Studio’s locals, watch, call stack for your scripts and modules
  • Use the PowerShell interactive REPL window to execute PowerShell scripts and command right from Visual Studio
  • Automated Testing support using Pester


An improved editing experience offers syntax highlighting, IntelliSense and code folding. You can quickly navigate your scripts with a function selection drop down.
A rich debugging experience allows you to execute and single step through local and remote scripts. With support for breakpoints, the locals window and the call stack window you can easily find and fix bugs in your scripts.
Support for running utilizing features such as DSC, Workflows and 64-bit modules (e.g. Sharepoint).
The PowerShell Interactive Window provides instant execution with IntelliSense and remote session support.
A project system is available to organize scripts and easily integrate with source control systems. It also offers a mechanism to provide module information for use in MSBuild scripts.
Test adapter support for discovering and running Pester tests.

$ErrorActionPreference = 'Stop'

$packageArgs = @{
    PackageName  = $env:ChocolateyPackageName
    VsixUrl      = ''
    Checksum     = '4449B34B024E0177A6BB8F64319630167681602291562E98BC019E016839E1B6'
    ChecksumType = 'sha256'

Install-VisualStudioVsixExtension @packageArgs

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
Discussion for the PowerShell Tools for Visual Studio 2017 Package

Ground Rules:

  • This discussion is only about PowerShell Tools for Visual Studio 2017 and the PowerShell Tools for Visual Studio 2017 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 PowerShell Tools for Visual Studio 2017, 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