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

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

    Resolution Note (fix version 2019.3):

    Fixed in 2019.3.13f1

Comments (17)

  1. Cf547544bceb8a14ed307edd0b97daf0?d=mm

    winklerglinesnw370

    Nov 30, 2020 08:26

    <a href="dsZCFgxhjfsdZCGxhjdscgzxhb">fdzcxghjksdzcxghjk</a>

    [url=wfsdgchxzjkfsdvzgcxhj]efasdgzhcjkfasdzhj[/url]

  2. 18e4e1321b70fc9fa55facae295b1168?d=mm

    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.

  3. Ee38139ed3fc8836d92c270c0dd83f74?d=mm

    FredZvt81

    Oct 24, 2020 20:32

    Got this error on 2019.4.12f1.

  4. 682a6d7183639038daf8a4b6c5db33d0?d=mm

    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.

  5. 18e4e1321b70fc9fa55facae295b1168?d=mm

    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.

  6. 18e4e1321b70fc9fa55facae295b1168?d=mm

    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.

  7. A34bcec72661c8d04979c9e81e8641e5?d=mm

    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

  8. 978ceddf645a6aa27b13068a4097042b?d=mm

    strictly9jaofficial

    Sep 05, 2020 06:33

    nice

  9. A0a2b4c79e7ca8dc486ee5f36bb2fb0d?d=mm

    RKeown3D

    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!!

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.