nice

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

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.

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

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

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>");
}
}

Also effects Visual Studio 2019

@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).

Any work around method?