VS Code Is Always A Problem

Every time I start a new project or upgrade an existing one, I have to monkey around and delete various files and folders to prevent these errors -- sometimes having to roll back various packages such as Visual Studio Code Editor. This time I'm having no such luck. It's really odd how these packages are 2020.1 Verified when I'm having so much trouble with sheer basics. If there's a set of steps to take manually, where do I find them? Also, why is this requiring manual action?

 

There could be somethng in the Hub saying we want or not do add VSCode and Rider to new projects

 

What OS are you running on? On OS X with VS Code I find I always need to roll back to the .3 version of the package to avoid the errors. I do not have the full Visual Studio package enabled. See this thread: https://forum.unity.com/threads/vis...the-referenced-project-does-not-exist.806628/

 

Windows 10
I rolled back to .3, but the issue remains.

Could Rider be the root of the issue?

I'd really like to fix this as I haven't been able to work on anything for days now. Any other ideas?

 

don't really see what vscode has to do with your error?
my guess off your log is you have a compile error stopping packages loading.

show us your manifest

 

Spoiler: manifest.json

Code (CSharp):

1. {
2.   "dependencies": {
3.     "com.unity.collab-proxy": "1.3.7",
4.     "com.unity.ide.rider": "2.0.2",
5.     "com.unity.ide.visualstudio": "2.0.0",
6.     "com.unity.ide.vscode": "1.1.4",
7.     "com.unity.test-framework": "1.1.11",
8.     "com.unity.textmeshpro": "3.0.0-preview.1",
9.     "com.unity.timeline": "1.3.0-preview.6",
10.     "com.unity.ugui": "1.0.0",
11.     "com.unity.modules.ai": "1.0.0",
12.     "com.unity.modules.androidjni": "1.0.0",
13.     "com.unity.modules.animation": "1.0.0",
14.     "com.unity.modules.assetbundle": "1.0.0",
15.     "com.unity.modules.audio": "1.0.0",
16.     "com.unity.modules.cloth": "1.0.0",
17.     "com.unity.modules.director": "1.0.0",
18.     "com.unity.modules.imageconversion": "1.0.0",
19.     "com.unity.modules.imgui": "1.0.0",
20.     "com.unity.modules.jsonserialize": "1.0.0",
21.     "com.unity.modules.particlesystem": "1.0.0",
22.     "com.unity.modules.physics": "1.0.0",
23.     "com.unity.modules.physics2d": "1.0.0",
24.     "com.unity.modules.screencapture": "1.0.0",
25.     "com.unity.modules.terrain": "1.0.0",
26.     "com.unity.modules.terrainphysics": "1.0.0",
27.     "com.unity.modules.tilemap": "1.0.0",
28.     "com.unity.modules.ui": "1.0.0",
29.     "com.unity.modules.uielements": "1.0.0",
30.     "com.unity.modules.umbra": "1.0.0",
31.     "com.unity.modules.unityanalytics": "1.0.0",
32.     "com.unity.modules.unitywebrequest": "1.0.0",
33.     "com.unity.modules.unitywebrequestassetbundle": "1.0.0",
34.     "com.unity.modules.unitywebrequestaudio": "1.0.0",
35.     "com.unity.modules.unitywebrequesttexture": "1.0.0",
36.     "com.unity.modules.unitywebrequestwww": "1.0.0",
37.     "com.unity.modules.vehicles": "1.0.0",
38.     "com.unity.modules.video": "1.0.0",
39.     "com.unity.modules.vr": "1.0.0",
40.     "com.unity.modules.wind": "1.0.0",
41.     "com.unity.modules.xr": "1.0.0"
42.   }
43. }

 

VS Code has a number of issues right now. You need to be on:
package 1.1.3 in the Unity Package manager
VS Code 1.42.1
C# extension 1.21.15 or 1.21.12
Debugger for Unity extension 2.7.5 or 2.7.3

See this thread if you want more info:
https://forum.unity.com/threads/psa...on-stopped-working.841255/page-2#post-5640583

 

yikes that sounds painful

 

I couldn't get it to work following your suggestions and those in the other thread. How unfortunate. Typically I don't have time to work on my projects, but everything runs fine when I do. Now I have all the time in the world due to quarantine, but nothing works.

 

https://www.jetbrains.com/rider/nextversion/

(note I linked the early access version because it doesn't require a subscription. you can kind of just keep using that indefinitely if you don't qualify for a free license or can't afford it.)

 

Assuming you did, but just in case you missed it, there was a suggestion that you need to shut down all VS Code processes via task manager on Windows. Can't remember if that was in one of the linked threads or if I saw that somewhere else.

 

I still find it very flakey using VS Code with Unity... even when on these suggested versions
- Have to restart OmniSharp a couple of times for VS Code to even know what a Vector3 is
- Can never see files in packages automatically (unlike Rider), I have to always manually add \Library to be able to navigate package libraries

It's a shame, I remember VSCode was just 'magic' about 1 year ago with Unity ...loads super fast, everything just worked