Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
13
Found in
2018.4
2019.3.3f1
2020.2
Issue ID
1240545
Regression
No
[Mono] .NET 4.7.1 standard/framework .XML files with useful descriptions are missing
Reproduction steps:
1. Go to "Unity\Editor\Data\MonoBleedingEdge\lib\mono\4.7.1-api"
2. Check if ".XML" files are there
Expected result: .XML" files with function descriptions are included with Unity installation
Actual result: ".XML" files are missing
Reproducible with: 2018.4.25f1, 2019.4.4f1, 2020.1.0b16, 2020.2.0a18
Note: The ".XML" files can be found at .NETFramework instalattion directory ("C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.7.1")
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
- Joint Physics result in unexpected behaviors when used for articulated vehicles like buses or trucks
- Standalone Player crashes with "TDerived GetOrLoad<TDerived>() where TDerived : T" when IL2CPP Code generation is set to "Faster (smaller) Builds"
- IndexOutOfRangeException and InvalidOperationException when logging XML string
- Script missing in "Assets/Settings/Mobile_Renderer/GlobalVolumeFeature" of "com.unity.template.urp-blank" template
- “Font Asset Creator - Error Code [Invalid_File_Structure]…“ error is logged when generating Font Assets from fonts which worked with TMP Font Asset Creator
Resolution Note:
Currently XML API documentation is not shipped, but this is on our roadmap for the future. We cannot provide an ETA to complete this though.