vscode-adapter
vscode-adapter copied to clipboard
Shore up Supported Run Scenarios
Right now the way the run works is a bit of a hodgepodge, I would like to very definitively define the following run scenarios (with the bolded already implemented)
- Separate Process, Main Window, Std In/Out, Reuse Process - Ideally would go away for runspace approach
- Separate Process, Main Window, Std In/Out, Restart Process - Ideally would go away for runspace approach
- Separate Process, Reuse Runspace - Fastest but may be subject to artifacts
- Separate Process, Reset Runspace on every run - Slower but less likely to have artifacts, will not refresh for binary modules
- Separate Process, Restart Process on every run - Slow but best for binary modules
- PS Extension using RunCommand [Debug Profile] (Implemented Debug Only) - Run just does the same as mirror today
- Temporary PS Extension using RunCommand [Debug Profile] (Implemented Debug Only)
- PS Extension with runspace running Pester