Search Issue Tracker

Fixed

Votes

13

Found in

4.3.4f1

Issue ID

589492

Regression

No

"Moving File Failed" dialog displayed when debugging

CodeEditors

-

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)

  1. 36c65e3934745df83910152c6a077e4a?d=mm

    shubhamswaraj2021

    Aug 18, 2020 05:40

    good one <a href="https://www.lyricsauto.com">lyricsauto</a>

  2. 1b92d44022be00d45d8583d2f86f0d6f?d=mm

    wiwiges

    Jul 10, 2020 21:39

    Note the Debug.Log is commented out

    https://dlandroid.com/spotify-music/

  3. 996b272bc387d950930300ef609e11c4?d=mm

    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

  4. A4f21b77bb3cb5caf922bb8da07882e7?d=mm

    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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.