microsoft / poshtools

PowerShell integration for Visual Studio

PowerShell Tools for Visual Studio

PowerShell integration for Visual Studio.

Build status of adamdriscoll/poshtools:
Build status of microsoft/poshtools: (What's this?)

More information on Adam Driscoll's blog. To download the VSIX, please visit the Visual Studio Gallery.

PowerShell Tools for Visual Studio currently offers the following features.

Script Editor Enhancements

Syntax Highlighting with customizable fonts and colors

IntelliSense for variables, cmdlets and arguments

Project System

PowerShell Project Template

PowerShell MSBuild Project Options

Debugging

Breakpoint and Breakpoint Pane Support

Stepping

Locals Support

Call Stack Support

Data Tips

Testing

Pester Test Adapter

poshtools's Issues

PSVS execution with parameter with UI support

Partner is more looking for leveraging on PSVS to execute a PS script, however, only way to provide parameters for script to run is through REPL window(interactive window), which may not be desirable experience for partner.

Exploratory Testing

Set up remote runspace

We need to set up the remote runspace with the debugging events hooked up properly.

Tweak the .csproj files to run without absolute paths

We should be able to build locally without worrying about which specific directory we're in.

Create helper for Inter-process communication

We need a helper class to manage the inter-process communication to support Intellisense for 64 bit CmdLets, keywords, etc.

Support user prompt during debugging

Setup AppVeyor to build & run tests from Source

Just need to check in the yml file now.

Breakpoints on empty lines shouldn't be settable

Breakpoints on empty lines, eg, line 4, shouldn't be settable, as when we run/debug, we don't break on that breakpoint.

First time IntelliSense trigger occasionally takes much longer time than expected

Installing PSVS on a machine without Powershell version >= 3 installed will get an error dialog when starting VS.

Here is the error dialog:

Create an option to choose Bitness of Out of Proc execution

Create a VS option to choose Bitness of Out of Proc execution, so people can choose either x86, x64, or use System Default

Status Bar gets overridden by Powershell Intellisense

The Visual Studio status bar and coloring gets overridden by notifications that Powershell is active; this hides global status state.

Deisgn the VSService Interface

Create and design the relevant VSService

Defining a custom prompt no longer works

function prompt { return "Custom Prompt > " }

Enter the above into either a script or the REPL Window. ISE and prior behavior run & define the prompt as specified. This is no longer the case.

In Debug interactive window, no intellisense for command parameters.

E.g., I define a Cmdlet Get-Proc with a mandatory parameter ComputerName, after typing Get-Proc and dash, I cannot see parameter ComputerName showing in the auto completion list.

PowerShell syntax Errors should also show up in the error list

Right now, they're only in-line within the editor. For the full experience, we should have them in the ErrorList as well.

Minimize Inter-process communication

We need to select minimum necessary information that needs communicated inter-process

Prevent the tooling from being installed on unsupported platforms

Need to define the support matrix too.

Remove the Open in PowerShell ISE command?

After the next few iterations, should we remove the Open in PowerShell ISE command if we're installed in VS?

Themed 'Statement Separator' color not correctly assigned

Dark Theme's 'Statement Separator' color not correctly assigned, and thus defaults to black. This is due to a typo in the Theme file's name. 'StatementSeparator' vs 'Statement Separator'.

Ctrl+Space can trigger the auto completion

Implement ability to debug through statements which ask for User Input

Implement ability to debug through statements which ask for user Input

Perform Exploratory testing and other Test-related items.

Enable Setting the next statement for execution during debugging

Wcf channel broken and not able to auto recover after unhanded exception thrown on server

System.ServiceModel.ProtocolException

"This channel can no longer be used to send messages as the output session was auto-closed due to a server-initiated shutdown. Either disable auto-close by setting the DispatchRuntime.AutomaticInputSessionShutdown to false, or consider modifying the shutdown protocol with the remote server."

Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.PrepareCall(ProxyOperationRuntime operation, Boolean oneway, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at PowerShellTools.Common.ServiceManagement.DebuggingContract.IPowershellDebuggingService.SetRunspace(Boolean overrideExecutionPolicy)
at PowerShellTools.DebugEngine.Engine.Execute() in c:\Users\zhiyd\Documents\GitHub\outproc_dbg_local\poshtools\PowerShellTools\DebugEngine\Engine.cs:line 114
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()

Enable use of Immediate Window

Enable use of Immediate window during debugging.

PSEdit functionality

We need to implement the PSEdit functionality for remote script file downloading and rendering within the Visual Studio editor.

Test Issue

Please Ignore

• test
• test
• test2

Do the thing!

• More test
• Hello World

header

• Implement This Interface
• Implement That Interface

Typing is significantly slowed down with specific words, such as configuration presented in the text editor

Update contents of Project/SharedProject

We should update the contents of Project/SharedProject with more recent code from NTVS/PTVS's SharedProject, to absorb any/all of their recent fixes.

We will need to be cognizant about the risk of regression on #92 but at the moment, there aren't any other known diversions.

Should we continue to have support for in-proc processing?

Bringing this up as a question we should discuss and resolve.

Script edits should be saved automatically before Execute.

This is very annoying when trying to debug.

Connect with VS Debugger

Wire the events to VS Debugger events properly so that VS can behave accordingly during debugging.

Execute mode(ctrl+F5) with proper UI(e.g: run and stop) for script to run

There is a stop button on REPL window, which is designed for stopping existing execution of script from REPL. For people who is trying to execute script from the UI, that button does not help. We need either invent an "execution mode(like ctrl+F5)" which introduce some UI for run and stop button in VS, or we run everything over "debugging mode"(just without BPs). Powershell ISE has very vague border line between debug and run script.

Hook up errors to 64 bit out-of-proc

Entry point via REPL of remote session connection info

We need an entry point via REPL of remote session connection info to debug/execute from VS. This is specifically about debugging a remote session not an arbitrary process on a remote computer.

Logging for PSHostService(a.k.a out-proc)

Need a bit of infrastructure work to plugin the logging from remote process into existing logging mechanism PowerShellTools is currently using.

Need to be able to expand $dte [and other non-PS complex objects] in watch window

We cannot expand to view any of the properties of $dte

Entry point via UI of remote session connection info

We need an entry point via UI of remote session connection info to debug/execute from VS.

Allow for Programmatic calls to run PS Scripts

Do we need to cache user inputs in REPL window even after they clear the screen

ISE does cache all user inputs in REPL window, meaning even after you clear the console windows, you can still use up arrow key to go to the previous command or you can get IntelliSense for the variables defined in the previous commands though they are cleared from the console window.

Unable to develop using Dev14 [Visual Studio 2015]

Braces, brackets and parens should be automatically filled in

New colors are not readable in dark theme

Our colors aren't affected by theme. Because the colors are editable in the properties, but don't have a theme defined, this should be fairly simple to fix and add to the theming.

Implement ability to modify variables [From Watch] during Debug

Implement the ability to modify variables from watch window that are used in my PS Scripts during debugging.

[Intellisense] Importing module should support Intellisense when clicking TAB

In ISE, clicking TAB after type "Import-Module " will trigger Intellisense. ISE will search all available modules and automatically fill in the first matched one.

Control of out-of-proc PS

We need to have total control over the out-proc and figure out how Out-proc can load the necessary assemblies so that we can get the Intellisense completion list.

Create PSHost with Powershell Debugging suites

Create the PSHost supporting local/remote runspace with powershell debugging suites hooked up

Create relevant unit tests

Set DTE as variable into runspace by default