PowerShell / PowerShell/vscode-powershell
Add support for remote development on Windows Sandbox
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 1.9k
- Fork
- 548
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
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
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
La issue non indica file del repository, test o punti di ingresso. Inizia esaminando il materiale collegato su VS Code remote-development e gli strumenti Windows Sandbox a cui si fa riferimento; per considerare il lavoro completato sarebbe necessario concordare l’ambito e i criteri di accettazione per le funzionalità richieste.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- powershell, vscode
- Ambito
- devtools
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 20/100