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
-
anchalkapoormodel
Feb 27, 2021 05:30
-
yourseen
Feb 03, 2021 01:00
-
herryparker1
Jan 27, 2021 12:48
Thanks for sharing this useful information - http://issuetracker.unity3d.com/issues/referenceoutputassembly-key-is-set-to-false-in-project-references
-
snowinrain
Jan 20, 2021 03:44
In Package Manager, find "Visual Studio Code Editor" and upgrade to version 1.2.3 to fix the issue
-
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.
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
- Shader error db grows on each build
- Android ARCore build fails with 2019.4 due to outdated Gradle
- [tvOS] Visual artifacts are present when Ambient Occlusion is enabled and Dynamic Resolution is reduced
- Texture Importer Inspector throws errors when a built-in texture inspector is overwritten in C#
- Invalid AABB error is thrown when moving a Particle with Velocity over Lifetime and Limit Velocity over Lifetime modules
Resolution Note (fix version 2019.3):
Fixed in 2019.3.13f1