Search Issue Tracker
Fixed
Votes
50
Found in [Package]
1.1.4
Issue ID
VSC-9
Regression
Yes
[VSCode] OmniSharp project reference warnings are thrown in VSCode console when using VSCode 1.1.4
How to reproduce:
1. Create a new Unity project
2. Make sure that your External Code Editor is set to VSCode and VSCode package version is 1.1.4
3. Click on Assets > Open C# Project
4. Once the VSCode window is open, go to the Output tab and inspect OmniSharp Logs
Expected results: No warnings regarding the referenced project being missed are thrown
Actual results: Many "Expected project reference Unity.TextMeshPro.Editor.csproj to be already loaded for project Assembly-CSharp" warnings are thrown
Reproducible with: 2019.2.19f1, 2019.3.0f6, 2020.1.0a20
Reproducible with package version: 1.1.4
Not reproducible with package version: 1.1.3
Notes:
1. Downgrading VSCode package to version 1.1.3 fixes the issue.
2. Reproduced on Windows and MacOS.
Comments (26)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture displays visual artifacts and has a broken aspect ratio when it is imported in RGB 48-bit format
- Diagnostic Warning Resets When Navigating Away and Returning to Diagnostics Settings
- Checkbox Collides with Text in Shader Graph Preferences Settings
- Crash on mecanim::animation::TransformValuesFromClip when entering the Play Mode in a project with Animancer Pro v8
- Connection to Named Pipes fails when server and client are run
Chebn
Jan 30, 2020 16:05
Confirmed on Unity Version 2019.3.0f6 on OS X.
As SergioCarneiro said:
1.- Downgrading to 1.1.3
2.- Close Unity
3.- Removing C# Project files (*.csproj)
4.- Reopening Unity fixes it.
ConorArup
Jan 30, 2020 15:06
I have the same issue (Unity 2019.3.0f6 - Windows).
Downgrading the Visual Studio Code Editor package to 1.1.3 did not fix the issue.
Example of warning - this appears hundreds of times for each package.
[warn]: OmniSharp.MSBuild.ProjectManager
Expected project reference c:\Users\ProjectLocation\com.unity.multiplayer-hlapi.Runtime.csproj to be already loaded for project Assembly-CSharp
Teos
Jan 30, 2020 05:49
Confirmed with Unity 2019.3.0f6 on OS X.
Downgrading to 1.1.3 worked.
The issue came up after creating a new project and importing script files to it from another project.
After opening VSCode, OmniSharp started complaining the following among many others like it:
[warn]: OmniSharp.MSBuild.ProjectLoader
The referenced project 'Unity.VSCode.Editor.csproj' does not exist.
[warn]: OmniSharp.MSBuild.ProjectLoader
The referenced project 'UnityEngine.UI.csproj' does not exist.
nomaded
Jan 29, 2020 22:50
Can confirm Unity 2019.3.0f6 on Windows 10. Issue arose after upgrading a project from 2019.2.17 to 2019.3.0f6.
Downgrade to v1.1.3 fixed the issue for us.
sergiocarneiro
Jan 28, 2020 23:22
I have the same issue. Can't confirm those exact steps reproduce the error, but downgrading surely fixed it.
Steps to Fix:
1. Downgrade to v1.1.3
2. Close Unity
3. Remove all C# project files
4. Open Unity
colin_young
Jan 28, 2020 20:22
Can confirm with Unity 2019.3.0f5 on OS X.
Also can confirm 1.1.3 downgrade fixes issue.