I found a fix (or workaround) for my problem:
short version . I changed the msbuild omnisharp instance using uninstall Visual Studio 2017 Pro .
long version . A few months ago, I installed VS 2017 Pro to test the features, used them for 2 weeks in trial mode and forgot about it for several months.
About a week ago, I opened it (by accident: D) and received a notification that my trial period has expired, also VS is blocked. This did not bother me, because I did not use it. In @VahidN Link, I found that omnisharp uses the “most native” instance of msbuild that was installed, which in my case was one of the blocked VS 2017 Pro. 1 + 1 I did not install VS and I am good.
I will reinstall VS 2017 (Comunity) and leave a comment if it still works fine.
EDIT:: I reinstalled VS 2017, everything works fine, so the current solution updates VS 2017 , which I could not do because it was blocked.
source share