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.
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
- Sprite Atlas remains loaded in memory after scene change or unloading assets
- [Vulkan] Release memory after deleting image
- Referred style sheet stays dirty after saving when using the UIBuilder
- The Height map Amplitude is not working when using HDRP/LayeredLit
- Crash on internalABP::BoxManager::prepareData when entering Play Mode
Eristen
Jan 14, 2022 15:17
Using Unity 2020.35.f1 with Visual Studio Code Editor plugin v1.2.4, problem still persists. I solved it by:
- downgrading the plugin to 1.1.3,
- erasing the .sln and .csproj files,
- regenerating them,
- opening VSCode,
- and finally upgrading the plugin to 1.2.4
absurdnoize
Sep 10, 2021 15:51
Using VS Code and Unity 2020.1.14.f
I have the same issue. I am afraid to brake Intellisense, but so far no solution worked.
Jules86
May 05, 2020 09:47
The issue is present in 1.1.3 in 2019.3.4 on Windows 10.
Downgrading to 1.1.2 removes the errors in VS Code, but the intellisense / autocomplete still can't resolve the new references.
neomarian
May 04, 2020 00:21
Still not fixed
SongAngel
Mar 26, 2020 01:46
For me upgrading the project settings to Api compatibility level .NET 4.x fixed the problem. Downgrading the VS Code extension to 1.1.3 did not fix the issue. Running Arch Linux here.
gokhan_wroomm
Mar 24, 2020 22:54
The version I use 2019.3.5f1. I downgrading VS Code Editor 1.1.3 version but not fix my problem. When i entered c# Scripts, i cannot import using UnityEngine.AI so ı cannot use NavMesh.. Please help me for this problem.
[url=https://hizliresim.com/XrPUv7][img]https://i.hizliresim.com/XrPUv7.jpg[/img][/url]
[url=https://hizliresim.com/ij7IaX][img]https://i.hizliresim.com/ij7IaX.jpg[/img][/url]
unayozan
Mar 24, 2020 19:47
Solved this by going into the preferences, external tools, and set the "Generate all .csproj files." to true.
Using 2019.3.6f1, Windows 10, VS Code package version 1.1.4.
caglarenes
Mar 24, 2020 01:17
Reproducible with 2019.3.6f1 and package version 1.2.0 on Windows 10 and OSX 10.15
PhoenSXar
Mar 23, 2020 03:45
Reproducible with 2019.3.2f1 and package version 1.1.4 on Windows 10.
Reproducible with 2019.3.2f1 and package version 1.2.0 on Windows 10.
Kruczek
Mar 22, 2020 15:04
Reproduced on 2019.3.6f1, both packages 1.1.4 and 1.1.3 have the same issue.