Hello!
We’ve tried to move to Unity 2019.3.12 from 2019.3.11, but we started seeing weird issues on the Visual Studio side related to Assembly Definition files (.asmdef) upon update (we’re using them extensively to enable testing). Everything is properly referenced and performs normally inside Unity editor, but for some reason Visual Studio insists that those namespaces don’t exist and/or we’re missing an assembly reference.
I checked through Known Issues in 2019.3.12 (Unity 2019.3.12), but couldn’t find anything on this matter (except stuff related to IAPs related assemblies, which might be slightly related). I basically have 2 questions:
- Did anyone have a similar issue? If so, any tips/tricks to deal with these?
- Currently update isn’t critical for us, so we can easily wait for the patch/new-version. Any way of knowing what sort of issues new version has without updating and scratching your head for a few hours (beyond “Known Issues” mentioned above)?