> For the complete documentation index, see [llms.txt](https://docs.poshtools.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.poshtools.com/open-source-tools/visual-studio.md).

# PoshTools VS

PowerShell Tools for Visual Studio

PowerShell Pro Tools for Visual Studio adds a PowerShell-focused development experience to Visual Studio. It provides editor services, project templates, debugging, analysis, test discovery, packaging, and UI design tools for PowerShell scripts and modules.

Use this tool when Visual Studio is your primary IDE or when you want PowerShell project support alongside .NET development.

## Features

* Syntax highlighting and IntelliSense for PowerShell files.
* Local and remote script debugging.
* PowerShell project and item templates.
* Pester unit test discovery through the Visual Studio Test Explorer.
* PSScriptAnalyzer integration.
* Refactoring commands and go to definition.
* PowerShell Interactive Window.
* Script packaging and MSBuild integration.
* Windows Forms designer support.
* Windows PowerShell and PowerShell 7 support.

## Quick Examples

Create a PowerShell project from **File > New > Project**, select a PowerShell project template, and press **F5** to run or debug the script entry point.

Package a script from a project by configuring the PowerShell project properties or by using the MSBuild packaging task documented in [Packaging in Visual Studio](/open-source-tools/visual-studio/bundling-and-packaging-with-msbuild.md).

Design a Windows Forms UI from Visual Studio with the form item templates and designer documented in [User Interface Design](/open-source-tools/visual-studio/user-interface-design.md).

## Downloads

* [Visual Studio 2022 extension](https://marketplace.visualstudio.com/items?itemName=AdamRDriscoll.PowerShellToolsVS2022)
* [Visual Studio 2017 and 2019 extension](https://marketplace.visualstudio.com/items?itemName=AdamRDriscoll.PowerShellToolsforVisualStudio2017-18561)
* [Changelog](https://github.com/ironmansoftware/powershell-pro-tools/releases)

## More Information

* [Installation](/open-source-tools/visual-studio/installation.md)
* [System Requirements](/open-source-tools/visual-studio/system-requirements.md)
* [Project System](/open-source-tools/visual-studio/project-system.md)
* [Debugging](/open-source-tools/visual-studio/chapter1.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.poshtools.com/open-source-tools/visual-studio.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.