Search Issue Tracker
Won't Fix
Votes
2
Found in
5.6.0f3
Issue ID
929696
Regression
No
"No MonoBehaviour scripts in the file" error if classes of the script are inside the namespace
"No MonoBehaviour scripts in the file" error if classes of the script are inside the namespace and the one which derives from MonoBehaviour is not the first one declared.
Reproduction steps:
1. Open the attached project
2. Select "NameSpaceBugExample" script in the Project window
Expected: no error
Actual: "No MonoBehaviour scripts in the file <...>" error
Reproducible on: 5.4.5p2, 5.5.0p4, 5.6.0f3, 2017.1.0f2, 2017.2.0b2
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.