PowerShell / PowerShell/vscode-powershell

Add support for remote development on Windows Sandbox

Open
#4,495 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: VS Code Issue-Enhancement
Dominant language
TypeScript
Stars
1.9k
Forks
547
PR merge metrics
No merged PRs in 30d

Description

Prerequisites
  • I have written a descriptive issue title.
  • I have searched all issues to ensure it has not already been reported.
Summary

Windows Sandbox (WSB) provides a lightweight desktop environment to safely run applications in isolation. Software installed inside the Windows Sandbox environment remains "sandboxed" and runs separately from the host machine. (for more info click here

In the spirit of Microsoft's mission to empower every person and every organization on the planet to achieve more I think it would be extremely useful to add to the remote development features of VSCode the ability to:

  1. Run scripts and binaries developed on my host machine using VSCode in Windows Sandbox so that I can manage my working copy or repository in an environment that stores my changes while making it possible to run the code in a sandboxed windows environment. This is especially useful for testing PowerShell scripts that spin dev environments (because as a precondition they must run in a pristine environment).

  2. Have a context menu (right click) function that enables me to run a script or a piece of code in WSB in a similar way to what has been implemented in damienvanrobaeys/Run-in-Sandbox: Run PS1, VBS, EXE, MSI in Windows Sandbox very quickly just from a right-click (github.com) has implemented. Notice how you can extract and run PowerShell scripts using a context menu, this is advantageous because it empowers people to skip the copy paste and handling of the WSB process

  3. Configure WSB environments using a GUI in a similar way to what has been implemented in https://github.com/leestevetk/WSBEditor

Additional Information
Proposed Design

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or entry points. Start by reviewing the linked VS Code remote-development material and the referenced Windows Sandbox tools; done would require an agreed scope and acceptance criteria for the requested capabilities.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, vscode
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.