microsoft / microsoft/vscode-dotnettools

[BUG] Workflow not very discoverable for multi-solution folders

Open
#586 0 comments 0 reactions 1 assignee View on GitHub

@sayedihashimi is already working on this.

Since Oct 13, 2023.

area-solution enhancement
Dominant language
No language data
Stars
321
Forks
54
Avg merge
2d 19h
Merged PRs (30d)
2

Description

Describe the Issue

Problem:

When opening a folder with multiple solution files the notification prompt appears and one must click the "Choose to open" button in order to see the pick list of solution files to choose from. The notification prompt is easy to miss on larger monitors as it appears in the lower right corner. On my mulit-mon setup, the lower right corner of the right-most monitor is a horrible place to put something important. Won't see it. I tried this multiple times repo'g a customer complaint of the same behavior.

Solution:

If one clicks the "Choose to open" button and then dismisses the pick list, the Solution Explorer is activated and contains a big button (very discoverable) labeled "Open Solution". That UI is what one should see when opening a multi-solution folder. This should be presented regardless of the interaction with the notification UI.

Steps To Reproduce
  1. Open a mutli-solution file folder
  2. Fail to notice the notification UI in the lower right corner. This is especially easy to miss on dark theme and in a multi-mon setup with the VSCode window docked on the right-most monitor.
Expected Behavior

Easier to get to the solution that I actually want to open. Activate the Solution Explorer - it already has a big button labeled "Open Solution".

Environment Information
  • OS: I tried MacOS, but I assume this is a problem on all supported OSes.
  • C# DevKit - latest version

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.