René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Don't stop debugging after script execution in TemporaryIntegratedConsole","articleBody":"### Prerequisites\n\n- [X] I have written a descriptive issue title.\n- [X] I have searched all [issues](https://github.com/PowerShell/PowerShellEditorServices/issues?q=is%3Aissue) to ensure it has not already been requested.\n\n### Summary\n\nI use VSCode for developing PowerShell modules. For debugging, I create a PowerShell configuration in the `launch.json` file with `createTemporaryIntegratedConsole` option enabled. This allows for a dedicated PowerShell session for debugging that is easy to restart.\r\n\r\nIn `launch.json` configuration, if the `script` option is not provided, the debugger still waits after the `[TEMP] PowerShell Extension` console opens: the debugger works in interactive mode, and if a command executed in the console hits a breakpoint, the debugger pauses. This mode allows you to efficiently debug a module, rather than having to update a temporary script.\r\n\r\nIf commands are entered in the `script` property in `launch.json`, for example to load the module and set the environment, the script is executed by PES and then the debugging session is stopped, although the temporary console remains open. This makes it impossible to debug in interactive mode. This requires not filling in the `script` property and manually entering the initialization commands each time the debugging session is (re)started, which is not practical for daily use when you frequently need to start from scratch.\n\n### Proposed Design\n\nIt would be useful if the debug session did not close until the temporary console is closed (since the primary purpose of running a script this way is to debug). While this cannot be enabled by default for reasons I do not know, an option to enforce this behavior would be welcome and very useful for developers.\r\n\r\nI haven't found a similar request here, but I did find one in the `vscode-powershell` repository: https://github.com/PowerShell/vscode-powershell/issues/1168\r\n\r\nFor my part, I have implemented a workaround that meets this need, while waiting for an official solution, by modifying a line in the `ConfigurationDoneHandler.cs` file: https://github.com/jul-m/PowerShellEditorServices/commit/d864c898600b82dd9b33f5abf7d7327c8af7224b","author":{"url":"https://github.com/jul-m","@type":"Person","name":"jul-m"},"datePublished":"2024-09-21T01:57:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/2180/PowerShellEditorServices/issues/2180"}