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
- “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
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.