[Visual Studio Code Editor 1.1.4] Error: The referenced project does not exist

jasonatkaruna · January 9, 2020, 11:40pm

After upgrading to Visual Studio Code Editor 1.1.4 package (com.unity.ide.vscode@1.1.4), I’m receiving this error in my OmniSharp output:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1875,5): Error: The referenced project ‘Unity.InputSystem.csproj’ does not exist.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1875,5): Error: The referenced project ‘Unity.Addressables.csproj’ does not exist.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1875,5): Error: The referenced project ‘Unity.TextMeshPro.csproj’ does not exist.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1875,5): Error: The referenced project ‘Unity.ResourceManager.csproj’ does not exist.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1875,5): Error: The referenced project ‘Unity.Timeline.csproj’ does not exist.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1875,5): Error: The referenced project ‘UnityEditor.UI.csproj’ does not exist.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1875,5): Error: The referenced project ‘UnityEngine.UI.csproj’ does not exist.

bsgbryan · January 12, 2020, 11:04pm

I am receiving equivalent errors on macOS.

bsgbryan · January 12, 2020, 11:15pm

The problem is: the Visual Studio Code Editor package v1.1.4 adds the following to the project’s .csproj file for each installed package (the below example is the Mathematics package):

<ProjectReference Include="Unity.Mathematics.Editor.csproj">
  <Project>{5aac75fd-a7ec-6fd2-d64a-6e83653848dc}</Project>
  <Name>Unity.Mathematics.Editor</Name>
</ProjectReference>

I have not been able to find the named project anywhere. The error is correct - these projects do not exist. For me, downgrading to v1.1.3 of the package fixed the problems as the above sections were removed from the .csproj file.

greg-harding · January 13, 2020, 1:07am

I just had to revert back to v1.1.3 as well. It looks like v1.1.4 is trying to include a bunch of csproj’s that do not exist and causing thousands of errors.

The package manager says that v1.1.4 is a verified package too. Argh.

Bug filed: Case #1211057

Update: 24 Jan - QA @Domas_L repro’d the issue and it’s been sent to the fixing place

Update: 15 March - There is a new VSCode v1.2.0 package (unverified) that addresses project generation problems Case #1211057; (Code Editor Package for Visual Studio Code | Visual Studio Code Editor | 1.2.5)

jasonatkaruna · January 13, 2020, 7:10am

reverting back solved it for me as well

Brice-Joly · January 16, 2020, 8:50am

Same problem, reverting to 1.1.3 fixed this too.

ROBYER1 · January 17, 2020, 2:33pm

Same here, reverting produced some obsolete api errors and other issues. Will a fix be coming?

torano · January 18, 2020, 7:20am

Same. Waiting for a fix.

Rocco_B · January 20, 2020, 7:49pm

Just want to also bump this up as I had the same issue and also resolved it by downgrading the package to 1.1.3.

Edit: A note that my Unity version was 2019.3.0f5

ROBYER1 · January 21, 2020, 11:39am

@Domas_L are your team aware of this issue?

sakus · January 22, 2020, 9:08pm

Another bump from me… just updated only to find out that the 1.1.4 version of VS Code Editor package is utterly broken and Google led me here. 2019.3.0f5 on Mac. 1.1.3 works.

Domas_L · January 23, 2020, 11:07am

Hello! We’ve successfully reproduced this issue and forwarded it to our developers for further resolution. The case will be visible on IssueTracker once the page is generated:
https://issuetracker.unity3d.com/product/unity/issues/guid/1211057

greg-harding · January 23, 2020, 11:13am

Great, thanks for letting us know, Domas.

RogDolos · January 28, 2020, 2:46pm

Seems to still be an issue with the release of 2019.3.0f6, which installing automatically pushes to the latest package–

Which with this bug, really should not be “verified” for exactly this situation?

pb · January 29, 2020, 2:11pm

Yep same situation here - the upgrade from 0f5 to 0f6 last night forced the vscode package onto a KNOWN BAD VERSION.

Crazy!

jdtec · January 29, 2020, 5:05pm

wow I had to downgrade from the official 2019.3.r6 release back to r5 to fix this… Lost some time.

2019.3 releases have been a real painful experience.

I’m going to be far more cautious upgrading packages/Unity versions from now on.

jasonatkaruna · January 29, 2020, 5:31pm

Hey jdtec, you can manually downgrade the package to 1.1.3 after upgrading to 2019.3.0f6. Then you can have 2019.3.0f6 without the issues of 1.1.4.

jdtec · January 29, 2020, 5:56pm

Thanks, however, I did try that (and some other vscode package versions)… not sure why this didn’t work for me if it has for others. I had to downgrade my entire Unity version.

A slightly different but related problem is I’ve had to resort to debug log debugging for the last month or so because the debugger seems broken.

Can any of you guys use the vscode Unity debugger on Mac to set breakpoints at the moment? My debugger reports attaching ok but then the debug controls in vscode disappear and it seems to just crash/disconnect (doesn’t report disconnecting though)

greg-harding · January 29, 2020, 8:33pm

To be honest, this has been my last decade with debugging Unity on a Mac. It has been terrible, never connecting, beachballing, connecting and immediately disconnecting, etc. MonoDevelop used to beachball every time I tried to connect back in olden days Unity.

There was a tiny window a few years ago when Unity was releasing an updated debugger within the Xamarin ecosystem when debugging worked, then they stopped support when updating and then dropping MonoDevelop. VSCode debugging support has been mostly rubbish since we started using it. After it finally started connecting more reliably other problems made it useless, like not being able to set breakpoints that actually worked, or stepping in and out being completely broken.

The latest version of VSCode and the 1.1.3 package do connect and debug in the Editor better for me than earlier versions but it’s hard to break the habit of trusty old Debug.Log after all these years eg. we can’t connect VSCode debugging to iOS devices - connect and immediate disconnect. It’s never worked.

jdtec · January 29, 2020, 8:55pm

greg-harding:

To be honest, this has been my last decade with debugging Unity on a Mac. It has been terrible, never connecting, beachballing, connecting and immediately disconnecting, etc. MonoDevelop used to beachball every time I tried to connect back in olden days Unity.

There was a tiny window a few years ago when Unity was releasing an updated debugger within the Xamarin ecosystem when debugging worked, then they stopped support when updating and then dropping MonoDevelop. VSCode debugging support has been mostly rubbish since we started using it. After it finally started connecting more reliably other problems made it useless, like not being able to set breakpoints that actually worked, or stepping in and out being completely broken.

The latest version of VSCode and the 1.1.3 package do connect and debug in the Editor better for me than earlier versions but it’s hard to break the habit of trusty old Debug.Log after all these years eg. we can’t connect VSCode debugging to iOS devices - connect and immediate disconnect. It’s never worked.

I’ve come to appreciate the uses of debug logs that’s for sure! It’s also nice to have a debugger in the toolbox too.

Anyway I fixed it!

I got a more in-depth vscode extension error log to display by following advice here.

Searching on the error I got when the debugger crashed showed up this old thread from December.

I downloaded the preview unity debugger 3.0.1.vsix file recommended in that thread from here and then followed instructions here about how to install .vsix files with vscode.

Now I can step through code again