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
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
-
MrG
May 05, 2020 22:29
Also effects Visual Studio 2019
-
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).
-
LuviKunG
May 05, 2020 09:51
Any work around method?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2019.3):
Fixed in 2019.3.13f1