Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add option to disable "some projects had problem opening" warning popup
See original GitHub issueIn the latest version of VS Code, where the alerts are shown in the bottom right, I seem to get a stupid amount of these during a re-build.
“Some projects have trouble loading. Please review the output for more details.” “Some projects have trouble loading. Please review the output for more details.” “Some projects have trouble loading. Please review the output for more details.” . . . . Did we have a way of disabling this message? It’s showing 10 times during a build, and it’s annoying the life out of me.
It’s trying to warn me about using 4.6.1 references in a netcoreapp2 project (which I know might blow up, but I’m aware of the consequences and what I’m doing here).
[warn]: OmniSharp.MSBuild.ProjectLoader
Package 'FluentMigrator.Runner 1.6.2' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.0'. This package may not be fully compatible with your project.
Any way I can either disable all omnisharp popups or this ProjectLoader WARN in particular?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:7
- Comments:15 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
For whoever lands here looking for an answer, add the following to user settings
@rchande Sorry if this was unclear in my OP, but this issue is not with the location of the pop-up. It’s with the pop-ups presence in the first place. I don´t care it was moved from top center to bottom right. I care with the frequence of which I have to hit ESC to get rid of pop-ups that really are build/restore WARNs. This WARN msg could easily have been put into the build log instead of a pop-up, similarly to what VS does.
@DustinCampbell Yeah, I’m aware of ESC closing pop-ups. I just don’t get why OmniSharp has to push this in my face. Or why I need to hit ESC this often at all.
This is the second issue I’ve raised with OmniSharp pushing pop-ups in VS Code for no real good reason (imo). Am I really the only one finding pop-ups as a concept of feedback really intrusive? A pop-up should be last resort imo (ERROR/FATAL).