Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0p1
Issue ID
984727
Regression
No
Moving asmdef file together with scripts causes nonstandard compile errors
Steps to reproduce:
1. Open user attached project
2. Drag-and-drop the script and the asmdef file into the folder. Make sure to drag-and-drop both at the same time
3. Console outputs: Source file `Assets/NewBehaviourScript.cs' could not be found
Expected result: moving asmdef file together with scripts should not cause nonstandard compile errors
Reproduced in: 2018.1.0b1, 2017.3.0p1, 2017.3.0b1
Comments (1)
-
DrummerB
Jun 12, 2019 15:25
I believe this issue is breaking some CI tools. It also makes it more difficult to switch between branches of the project.
Example:
A - Initial commit
B - Another commit
C - Commit, where the above issue is introduced
D - Another commit
E - Latest commitIf I check out B, then try to check out E, I get the above compile error. If there are some branches at older commits (before C) and other branches on more recent commits (after C), then an automatic build tool will fail any time it goes from an older to a newer branch. Unless it runs a completely clean build every time, which ideally would only happen for the nightly build and not for the push-triggered incremental builds.
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.