- #VISUAL STUDIO CODE UNITY AUTOCOMPLETE NOT WORKING INSTALL#
- #VISUAL STUDIO CODE UNITY AUTOCOMPLETE NOT WORKING MAC#
- #VISUAL STUDIO CODE UNITY AUTOCOMPLETE NOT WORKING WINDOWS#
: Registered MSBuild instance: Visual Studio Enterprise 2019 6.143 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin" : Located 2 MSBuild instance(s) 1: Visual Studio Enterprise 2019 6.143 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin" 2: StandAlone 16.0 - "C:\Users\my_username\.vscode\extensions\ms-vscode.csharp-1.21.3\.omnisharp\1.34.4-beta.7\.msbuild\Current\Bin"
I have debugging on but didn't get the output you had referenced. This is what's showing in my OmniSharp Log. I actually have VS Enterprise 2019 installed so it sounds like I don't need to pick up the build tools. The latter will always be better though as the support in the built-in MSBuild in VS2019 / Mono will be always better than in the built in instance running on embedded Mono. It has always worked like that (for all VS versions) and it's the safest bet to resolve any issues.įor the embedded runtime - without VS/VS Build Tools/Mono - at the moment the best workaround would be to try #3290 (comment) or #3290 (comment).
#VISUAL STUDIO CODE UNITY AUTOCOMPLETE NOT WORKING INSTALL#
If you install VS 2019 or VS 2019 Build Tools (or Mono 6+ on *nix), OmniSharp will automatically pick it up instead of the embedded MSBuild and use that for language services - there should be no need to export any additional variables.
There are several other issues that cause certain problems though - especially with. It's just MSBuild 16 has assembly version 15.x which is why it shows up in the paths in a misleading way, with 15. NET Core 3.0 previews worked with OmniSharp before. OmniSharp ships with MSBuild 16 since April ( OmniSharp/omnisharp-roslyn#1444) - that's why. The reason for this workaround is apparently this: #3287 (comment) My apologies for the initial misinformed linking.
#VISUAL STUDIO CODE UNITY AUTOCOMPLETE NOT WORKING MAC#
Linux and mac can try installing mono 6 or newer per this comment #3290 thanks for the clarification! I've updated my comment to better reflect the facts.
#VISUAL STUDIO CODE UNITY AUTOCOMPLETE NOT WORKING WINDOWS#
Hopefully fixed for windows with OmniSharp/omnisharp-roslyn#1606 I think the problem is basically this #3290 It should be using msbuild from the new build tools you just installed rather than the one shipping with omnisharp. MSBuildExtensionsPath: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild VisualStudioInstallRootDirectory: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools MSBuildSDKsPath: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\SdksĬurrentMSBuildConfigurationFile: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\ĬurrentMSBuildExePath: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\MSBuild.exeĬurrentMSBuildToolsDirectory: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin MSBuildToolsDirectory64: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\amd64
MSBuildToolsDirector圓2: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin NET Core SDK (reflecting any global.json):īase Path: C:\Program Files\dotnet\sdk\2.2.402\ Logs OmniSharp log Post the output from Output->OmniSharp log here C# log Post the output from Output->C# here Environment information Some suggestions, no descriptions, no underlines. Expected BehaviorĮxpected underlines, suggestions, etc. Steps to Reproduceĭownloaded Unity, Downloaded Visual Studio Code, Installed C# Extension and recommended. It has not worked since I downloaded Visual Studio Code.
0 kommentar(er)
