Description:
When attempting to open a new MI project from a window with an existing project in VS Code, two options are provided: "Current Window" and "New Window". Selecting the "Current Window" option is expected to replace the existing project with the new one in the same window. However, the current behavior loads the new project alongside the existing one, resulting in neither project's content being displayed correctly. It appears that VS Code is inadvertently creating a workspace by keeping both project folders open simultaneously.
Description: When attempting to open a new MI project from a window with an existing project in VS Code, two options are provided: "Current Window" and "New Window". Selecting the "Current Window" option is expected to replace the existing project with the new one in the same window. However, the current behavior loads the new project alongside the existing one, resulting in neither project's content being displayed correctly. It appears that VS Code is inadvertently creating a workspace by keeping both project folders open simultaneously.
https://github.com/user-attachments/assets/50ee5468-46b2-4e52-830a-9a45062aca89
Suggested Labels: Area/MI Extension, bug
Suggested Assignees:
Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues: