PowerShell / PowerShell/vscode-powershell
Add support for remote development on Windows Sandbox
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 1.9k
- Forks
- 548
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
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:
-
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).
-
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
-
Configure WSB environments using a GUI in a similar way to what has been implemented in https://github.com/leestevetk/WSBEditor
Additional Information
- A link to a useful tool that is relevant and brings us closer to realize the goal stated above is https://github.com/jdhitsolutions/WindowsSandboxTools
Proposed Design
No response
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Das Issue nennt keine Repository-Dateien, Tests oder Einstiegspunkte. Beginne mit der Durchsicht des verlinkten VS Code remote-development-Materials und der referenzierten Windows-Sandbox-Tools; als abgeschlossen würde die Arbeit ein vereinbarter Umfang und vereinbarte Abnahmekriterien für die angeforderten Funktionen erfordern.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- powershell, vscode
- Bereich
- devtools
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 20/100