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. Response avatar

    Resolution Note (fix version 2019.3):

    Fixed in 2019.3.13f1

Comments (34)

  1. 682a6d7183639038daf8a4b6c5db33d0?d=mm


    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.

  2. 18e4e1321b70fc9fa55facae295b1168?d=mm


    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:

    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.

  3. 18e4e1321b70fc9fa55facae295b1168?d=mm


    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:

    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.

  4. A34bcec72661c8d04979c9e81e8641e5?d=mm


    Oct 16, 2020 02:55

    uuumm are you sure this is resolved? I'm getting the same behaviour on versions:

  5. 978ceddf645a6aa27b13068a4097042b?d=mm


    Sep 05, 2020 06:33


  6. A0a2b4c79e7ca8dc486ee5f36bb2fb0d?d=mm


    May 08, 2020 16:59

    I was chasing my tail for about 3 hours this morning, after upgrading from 2019.3.3f1 to 2019.3.12f1. I'm glad someone found it and posted the fix. I t was getting annoying as all hell!!

  7. 7dc5f71796cd382b3cd06993ea73dd5d?d=mm


    May 06, 2020 22:13

    This is fixed in 2019.3.13, both for new projects and existing projects upgraded from 2019.3.12 where they were broken in Visual Studio 2019.

  8. D2902caa35878747b755fa41c2a0b0e6?d=mm


    May 06, 2020 18:38

    @DRDRAXI Thank you, this worked after closing Visual Studio, deleting .vs folders and all VS files, and then reopening any script.

  9. 7e0bb26bcaf15c5187aead70fe83c662?d=mm


    May 06, 2020 10:47

    @Luvikung you can set it to 'true' in referencing .csproj files

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.