Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shore up Supported Run Scenarios #176

Open
JustinGrote opened this issue Jul 31, 2023 · 0 comments
Open

Shore up Supported Run Scenarios #176

JustinGrote opened this issue Jul 31, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@JustinGrote
Copy link
Collaborator

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)

  1. Separate Process, Main Window, Std In/Out, Reuse Process - Ideally would go away for runspace approach
  2. Separate Process, Main Window, Std In/Out, Restart Process - Ideally would go away for runspace approach
  3. Separate Process, Reuse Runspace - Fastest but may be subject to artifacts
  4. Separate Process, Reset Runspace on every run - Slower but less likely to have artifacts, will not refresh for binary modules
  5. Separate Process, Restart Process on every run - Slow but best for binary modules
  6. PS Extension using RunCommand [Debug Profile] (Implemented Debug Only) - Run just does the same as mirror today
  7. Temporary PS Extension using RunCommand [Debug Profile] (Implemented Debug Only)
  8. PS Extension with runspace running Pester
@JustinGrote JustinGrote added the enhancement New feature or request label Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant