Hello,
I have a problem with my VS Code when i start my project with 2018.2 version. After clicking on an c# File i get two empty opened editor windows with the file, each times and code correction does not work.
I know about the bug with namesspace in project name, but my project haven’t namespaces.
How to fix that?
1 Like
I was just getting ready to post a thread on this as well. I have the exact same issue. Visual Code appears to be a dead stick after the upgrade.
No intellisense, and the opening up of two empty files seemingly associated with the project.
My bad for not checking the forums before updating…
I just uninstalled the latest update for now which sucks but I just don’t have the time to lose messing with this at the moment. After reinstalling the previous version 2018.1.7f1. Visual Code worked as expected.
I can’t be totally sure but it seems like Unity is not generating a project file that Visual Code can work with or recognize.
Who knows 
I guess I’ll keep checking back and update when it’s ready for primetime against VSCode.
After seeing this post I decided to reinstall the new version again.
As per the complaint in the post I linked. I didn’t have a space in the name of my project. However, I did have a space in the name of one of the folders in the project path, eg. “/Unity Projects”. After changing that folder name to “/UnityProjects” everything related to this particular issues seems to be resolved.
4 Likes
Thank you FocusedBit, your solution works for me too!
1 Like
Glad it helped you out 
It was frustrating for me too.
If renaming folders is out of the question for some reason, there’s a one simple workaround: Click the Open folder button in VS Code to open your project folder that way. This allows you to keep working, but you still won’t be able to double click console messages to skip to the correct places in scripts, which is a major drawback.
I don’t have any spaces in my project path/structure and Intellisense is still not working for me, though I never had the tab-opening issue originally reported; I only mention this as @CuriousScribbles brought up Intellisense.
The issue with spaces in the file path is fixed in Unity 2018.2.1f1. I don’t know if that issue affected Intellisense? Everything seems to work fine for me now.
I don’t think the spaces were affecting Intellisense either (now), I brought it up because someone else had.
For anyone else brought here by a search that has issues with Intellisense, the following link is where you want to post:
https://discussions.unity.com/t/709839
That’s what I did:
-
Right-click the script ypu want to edit.
-
After VSCode starts, close all scripts and (Here comes the trick) open you script on the VSCode by cliking in on the left menu and Ta-dahhhhh! It works!
Here is my screen:
So…why is this bug still in 2019.2 and 2019.3?
open VS Code from Unity (Assets/Open C# Project) and all works fine.