Release Notes – July Maintenance Release

PowerShell Tools for Visual Studio has been updated! See below for release notes.

PowerShell Tools

  • Version 3.0.582
  • July 7th, 2017


Visual Studio 2017
Visual Studio 2015

Issues Resolved

#542 – New Powershell projects in VS 2015 do not include “<Target Name=”Build” />” in the .pssproj file, breaking the build

MSBuild support for VS2015 broke “building” of PowerShell projects. The C# compile was being used to try and compile PS1 files resulting in build errors. This fix resolves the issue for new projects. Please see the GitHub issue for manual resolution steps if you are experiencing this problem.

#540 – Generated manifest file contains incorrect RootModule sample

Manifests in the PowerShell Module Project template included the PSD1 file as the RootModule which would fail to load. 

Documentation Updated

PowerShell Interactive Window

PowerShell Pro Tools

Version 1.0.90 (vs2015) and 1.0.89 (VS2017)

June 23rd, 2017


Visual Studio 2017
Visual Studio 2015

Issues Resolved

Bundling and Packaging

Bundling and packaging is now available via a command line tool, a PowerShell module and within Visual studio. Bundling allows you to combine multiple dot sourced scripts into a single script. Packaging wraps PowerShell scripts in .NET executables. Bundling can be combined with packaging. You can bundle and package via MSBuild and the PowerShell project system.

You will need to upgrade your existing projects to take advantage of the MSBuild tasks.

#1 – Packaging a Windows Form as Executable

PSPack and Package as executable feature now support bundling multiple files into a single executable. You can use the bundling feature to combine multiple PS1s into a single PS1.

#4 – Invalid Script Generated in XAML Designer

Fixed an issue where the XAML designer would generate an invalid script when adding multiple controllers with event handlers.