Search Issue Tracker
Fixed
Votes
13
Found in
4.3.4f1
Issue ID
589492
Regression
No
"Moving File Failed" dialog displayed when debugging
Receive a crash prompt saying: "Moving File Failed - Moving Temp/Assembly-CSharp.dll.mdb to Library/ScriptAssemblies/....Access is denied" when debugging.
Repro:
1) Create a script with the following code. Note the Debug.Log is commented out.
```
using UnityEngine;
public class TestScript : MonoBehaviour {
void Start () {
// Debug.Log ("Start"); // breakpoint here
}
}
```
2) Place a breakpoint on the commented line. It will automatically move to the next line, that is expected. Attach MonoDevelop to the Editor.
3) Enter playmode in the Editor. The debugger will stop at the end of the Start function.
4) Press the continue button in MonoDevelop. Don't switch to Unity just yet.
5) Uncomment the commented line. Save your changes.
6) Switch back to Unity. At this point Unity will try to compile the code and will throw the "Moving file failed message"
Comments (4)
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
- [Usability] “Sorry, no templates match the search “”” message is not informative when creating a new Project in the Hub with Custom Template filtering enabled but no Custom Templates created
- AI Assistant upgrade banner's `Open package Manager` link doesn't work
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Selection highlight is drawn in an Animation Window when clicking in another Animation Window after highlighting items in the first one
AlkisFortuneFish
Nov 13, 2014 10:26
Lukasz has posted a patch over at the forum, people may want to test if it works for them.
http://forum.unity3d.com/threads/4-3-x-monodevelop-breakpoints-not-working.215444/page-2#post-1842552
meakeel
Jul 01, 2014 11:22
To me this looks like the sort of problem I get when I use multiple projects in ASP.NET to build up DLL's for the "master" project.
The Mono Develop copy isn't matching the Unity compiled version which is what is stopping the breakpoints.
I've been able to sort it a couple of times but it's a pain to have to spend 30-60 minutes trying to get them to re-sync.