Search Issue Tracker

Fixed in 2019.3.X



Found in


Issue ID




ReferenceOutputAssembly key is set to false in project references



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

  1. Resolution Note (fix version 2019.3):

    Fixed in 2019.3.13f1

Comments (23)

  1. smithjohns402

    Jun 09, 2024 09:05

    If Visual Studio isn't recognizing certain types in your Unity project, it's likely due to a compatibility issue or misconfiguration. First, ensure both Unity and Visual Studio 2017 are compatible and properly set up. Try reimporting assets in Unity and rebuilding the solution in Visual Studio. Check scripting define symbols and references, and update extensions if applicable. If problems persist, seek help from Unity or Visual Studio communities. Restarting both programs may also help. With these steps, you should be able to troubleshoot and resolve the issue efficiently.

  2. Rolaif

    Dec 13, 2023 05:43

    I Like this post thanks

  3. james467798043

    Aug 24, 2023 07:54

    Thank You So much this is very helpful information.

  4. cprenoveau

    Sep 21, 2022 15:03

    Experienced the issue in 2020.3.14 with Visual Studio 2019 and 2022
    Issue no longer observed in 2021.3.10

  5. herryparker1

    Jan 27, 2021 12:48

  6. 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

  7. 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:

    So update the package `com.unity.ide.vscode` to version 1.2.3 and everything should be working again.

  8. FredZvt81

    Oct 24, 2020 20:32

    Got this error on 2019.4.12f1.

  9. 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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.