-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Test omnisharp installation hint #2701
Comments
The experience is bad without some progress indication, filed #2835 |
I agree with @egamma, while it works, the experience is pretty bad without any progress indication. But I also agree that we should take some time to think about how best to design a solution to this. |
The OmniSharp extension is being slimmed down to remove the runtime, such that the runtime will be installed on first activation. That means the extension should install quickly and then there will be UI to install the rest. @DustinCampbell is working on the install experience now. |
From my testing: The prompt is useful but it is easy to miss it and it never comes up again. Maybe I don’t want to install it right now, because I opened the tool on the wrong folder, etc. If I bring up the tool, get the prompt, and press Cmd+Q to exit Code I'll never get the prompt again. I put a suggested experience in #2748, which is effectively to have a yes/no/later prompt and to only write the "do not prompt again" flag if the user presses "no". |
Assignment
Details
We plan to make omnisharp an optional extension. To make a smooth transition we let the user know once and offer a direct install.
*.cs, project.json, *.csproj
etc)Make sure
global://extensionsAssistant/legacy...
)The text was updated successfully, but these errors were encountered: