Closed Rwprice closed 7 years ago
@Rwprice it looks like you have an environment variable called MsBuild
with the value C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\MSBuild.exe
.
Due to a bug, this conflicts with internal OmniSharp configuration (at the moment it "reserves" MsBuild
env variable for itself).
This will be fixed in OmniSharp soon - but in the meantime, you can rename/remove that environment variable to fix your issue.
As a workaround, you can unset your "msbuild" environment variable before starting VS Code.
Hi, It will be great, if you tell us how to unset it for Vscode
@developerTN just run command like:
unset msbuild
Issue happening with Unity Engine at the moment, not sure if it is a problem with VSCode or the engine itself.
Environment data
dotnet --info
output: .NET Command Line Tools (1.0.4)Product Information: Version: 1.0.4 Commit SHA-1 hash: af1e6684fd
Runtime Environment: OS Name: Windows OS Version: 10.0.10586 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\1.0.4
VS Code version: C# Extension version: 1.12.2
Steps to reproduce
Open a C# project folder in VsCode with Omnisharp extension installed, view logs.
Expected behavior
Intellisense begins working
Actual behavior
Intellisense does not begin working
Logs