Search Issue Tracker
Fixed in 2019.3
Votes
24
Found in
2019.3.12f1
Issue ID
1243277
Regression
Yes
ReferenceOutputAssembly key is set to false in project references
Steps:
1. Set External Tools to Visual Studio 2017 in Unity Editor
2. Open attached project
3. Double-click on any script in Assets -> Examples -> Scripts folder
4. In the Visual Studio 2017 solution Expand NavMeshComponents project
5. Double-click on NavMeshAssetManager.cs
6. => Studio highlights the types it cannot find in red
Reproducible with: 2019.3.12f1
Not reproducible with: 2018.4.22f1, 2019.3.11f1, 2020.1.0a1, 2020.1.0b8, 2020.2.0a9
-
bestgamingbeasts
Dec 25, 2020 19:59
bestgamingbeasts.com/how-many-watts-does-a-laptop-use/
-
winklerglinesnw370
Nov 30, 2020 08:26
<a href="dsZCFgxhjfsdZCGxhjdscgzxhb">fdzcxghjksdzcxghjk</a>
[url=wfsdgchxzjkfsdvzgcxhj]efasdgzhcjkfasdzhj[/url]
-
peabnuts123
Nov 22, 2020 23:56
I have received an update from Unity that this issue has been resolved in `com.unity.ide.vscode@1.2.3`. You can see the changes to the code mirrored here: https://github.com/needle-mirror/com.unity.ide.vscode/commit/efa6bd0ed1ed0129f6f5c47c81f1d4b2bbd9ac53.
So update the package `com.unity.ide.vscode` to version 1.2.3 and everything should be working again.
-
FredZvt81
Oct 24, 2020 20:32
Got this error on 2019.4.12f1.
-
joeccleung4SmashingIdeas
Oct 22, 2020 15:46
Thank you @peabnuts123 for the workaround. I am new to issue tracker and not sure where to file this issue.
-
peabnuts123
Oct 19, 2020 23:57
UPDATE: It turns out com.unity.ide.vscode@1.1.4 is utterly broke as well, see Unity forum thread: https://forum.unity.com/threads/visual-studio-code-editor-1-1-4-error-the-referenced-project-does-not-exist.806628/
1.2.0 was a release to address this issue. It seems the recommendation at the moment is to actually roll back to 1.1.3. This is (finally) working correctly for my on my machine.
-
peabnuts123
Oct 19, 2020 23:43
A regression has been made in the package com.unity.ide.vscode since v1.2.0 that re-introduces this property in generated csproj files, breaking external compilers.
You can see it in the code mirrored here: https://github.com/needle-mirror/com.unity.ide.vscode/blob/168d16ca32f5864f8b9332b440c538b8171850bc/Editor/ProjectGeneration/ProjectGeneration.cs#L479
If you revert back to com.unity.ide.vscode@1.1.4 then this problem goes away (though you lose the "Regenerate project files" button in settings - automatic generation still works). I've raised a ticket with Unity to remove this from the package, will comment here again when it is updated.
-
chantey
Oct 16, 2020 02:55
uuumm are you sure this is resolved? I'm getting the same behaviour on versions:
2020.1.6
2020.1.9
2020.2.0b7 -
alexerd
Sep 21, 2020 06:45
-
strictly9jaofficial
Sep 05, 2020 06:33
nice
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
- Nodes in the Vertex block are deleted when the edge connected to the Node is deleted
- Changes to instanced detail mesh material don't immediately apply
- [uGUI] Vertices retrieved from GetUIVertexStream method cannot be modified when adjusting them through script
- Scroll bar scrolls less in the Package Manager packages than elsewhere when pressing on the empty scroll bar area to scroll
- Undo.RegisterCreatedObjectUndo dirties the scene, but no actual changes to Scene are made
Resolution Note (fix version 2019.3):
Fixed in 2019.3.13f1