Search Issue Tracker
Fixed in 1.0.11
Votes
0
Found in [Package]
1.0.2
Issue ID
1156795
Regression
Yes
[Visual Studio] .csproj and .sln files are generated incorrectly causing Visual Studio to not understand Unity types
How to reproduce:
1. Open any project in 2019.2.0a12 or above and install Visual Studio Editor package
2. Write any Unity related script in any file (for example something containing GameObjects or Transforms)
-- Observe the console errors
Reproduced with: 2019.3.0a4 with package version 1.0.2 and 1.0.10
Couldn't reproduce on any 2019.2 version with any package version.
Note: Different kind of errors in 2019.3.0a1.
Errors:
NullReferenceException: Object reference not set to an instance of an object
UnityEditor.Experimental.AssetImporters.AssetImporterEditor.InternalSetTargets (UnityEngine.Object[] t) (at C:/buildslave/unity/build/Modules/AssetPipelineEditor/ImportSettings/AssetImporterEditor.cs:122)
UnityEditor.Editor.OnForceReloadInspector () (at C:/buildslave/unity/build/Editor/Mono/Inspector/Editor.cs:603)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
Add comment