Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0p1
Issue ID
986830
Regression
No
[asmdef] Assembly Definition file name does not match ‘Name’ value in Inspector after renaming
Steps to reproduce:
1. Create new Unity project
2. Create new Assembly Definition in Project window
3. Deselect asset
4. Rename the created Assembly Definition
Expected results:
Asmdef file name in Project window and Inspector ‘Name’ field match
Actual results:
Asmdef file name in Project window is changed and Inspector ‘Name’ field remains unchanged
Reproduced in: 2018.2.0a1, 2018.1.0b3, 2017.3.0p3, 2017.3.0b1
Note: Changing ‘Name’ value in Inspector does not change the file name either
------------
By design:
This works the same way as when renaming MonoBehavior scripts. We create the MonoBehaviour script with the same name as the filename, but we do not rename the MonoBehaviour class when renaming the file.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment