Search Issue Tracker
By Design
Votes
1
Found in
2022.3.58f1
6000.0.40f1
6000.1.0b8
6000.2.0a5
Issue ID
UUM-98166
Regression
No
Warnings are not logged in the Console window when using external code analyzers
How to reproduce:
1. Open the “VSWarningTest” project
2. Reimport “Assets/FooBehaviour.cs”
3. Observe the Console
Expected result: Warning is displayed
Actual result: No warnings are visible
Reproducible in: 2022.3.58f1, 6000.0.40f1, 6000.1.0b8, 6000.2.0a5
Reproduced on: Windows 10
Not reproduced on: No other environment tested
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
- Particle System Renderer icon is missing in Animation window > Add Property context menu
- [Android] Legacy, TMP and UI Toolkit Input Field language toggle to some non-latin alphabet languages does not work with external keyboard
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
- Scene View Camera overlay preview goes out of Scene View bounds when the Scene View is resized vertically
Resolution Note:
In order to roslyn analyzers/source generators to work they need to placed under Assets/ folder (https://docs.unity3d.com/Manual/create-source-generator.html)
The reason for that is that Editor will not import assets outside `Assets/` folder whence compilation pipeline will not include the analyzer.
The fact that the analyzer is included in the .csproj does not affect this because Unity does not use the .csproj in the build.