Search Issue Tracker

Fixed in 2019.3.X

Votes

24

Found in

2019.3.12f1

Issue ID

1243277

Regression

Yes

ReferenceOutputAssembly key is set to false in project references

Scripting

-

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

  1. Resolution Note (fix version 2019.3):

    Fixed in 2019.3.13f1

Comments (27)

  1. ftgg356po

    Jun 22, 2025 00:27

    Unity

  2. essentialpicks24

    Jun 12, 2025 15:48

    Appreciate the workaround, @peabnuts123 — that pointed me in the right direction. I'm still getting used to how this issue tracker works, so not quite sure where exactly to log this properly.

    sattaking-superfast.com

  3. essentialpicks24

    Jun 12, 2025 15:47

    Appreciate the workaround, @peabnuts123 — that pointed me in the right direction. I'm still getting used to how this issue tracker works, so not quite sure where exactly to log this properly.

  4. essentialpicks24

    Jun 12, 2025 15:47

    Appreciate the workaround, @peabnuts123 — that pointed me in the right direction. I'm still getting used to how this issue tracker works, so not quite sure where exactly to log this properly.

  5. hackson023

    Aug 21, 2024 09:21

    I encountered the same issue when working on a recent project. Setting the ReferenceOutputAssembly key to false in project references led to unexpected behavior. It would be helpful if the documentation provided more clarity on this setting and its implications. Anyone else find a workaround or best practice for handling this? drywallsurreybc.com

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

  7. Rolaif

    Dec 13, 2023 05:43

    I Like this post thanks

  8. james467798043

    Aug 24, 2023 07:54

    Thank You So much this is very helpful information.

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

  10. herryparker1

    Jan 27, 2021 12:48

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.