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

Log in to vote on this issue

Comments (37)

  1. MrG

    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.

  2. lumeriith

    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.

  3. otez

    May 06, 2020 10:47

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

  4. Draxi_

    May 06, 2020 10:47

    I found this piece of code on some forums few days after 12f1 was released. Just put this script somewhere inside your Assets folder and it should "fix" your .csproj file on import.

    (Replacing these lines by hand won't work. They will change back to false everytime the script gets changed -> saved -> reimported)

    using UnityEditor;
    public class FIX : AssetPostprocessor
    {
    private static string OnGeneratedCSProject(string path, string content)
    {
    return content.Replace("<ReferenceOutputAssembly>false</ReferenceOutputAssembly>", "<ReferenceOutputAssembly>true</ReferenceOutputAssembly>");
    }
    }

  5. MrG

    May 05, 2020 22:29

    Also effects Visual Studio 2019

  6. Seith

    May 05, 2020 11:54

    @Luvikung None, except reverting your project to 2019.3.11f1 (not sure how feasible that would be) or switching to Visual Studio Code (which is not affected by this bug).

  7. LuviKunG

    May 05, 2020 09:51

    Any work around method?

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.

Latest issues

See all new issues