I just finished a debugging session, the console for the old process is gone, and the Xamarin Studio GUI left 'Debug View' going back to 'Solution View'. But when I try to run or debug the same project again, it rebuilds and fails on the error below.
This happens the majority of the time after a debugging session, but not 100% of the time. The only fix I have is to close Xamarin Studio.
This only happens when Active Runtime is Mono. It doesn't happen when Active Runtime is MS. (But when Active Runtime is MS the debugger doesn't let me inspect anything so that isn't a usable alternative).
It does sound a lot like Bug 5295, but its happening in 4.2.2, current Stable.
----- Builder Error Message -----
Copying file from 'C:\Dev\gitsrc\Cheese\Cheese\obj\Debug\Cheese.dll.mdb' to 'C:\Dev\gitsrc\Cheese\Cheese\bin\Debug\Cheese.dll.mdb'
Copying file from 'C:\Dev\gitsrc\Cheese\Cheese\obj\Debug\Cheese.dll' to 'C:\Dev\gitsrc\Cheese\Cheese\bin\Debug\Cheese.dll'
C:\Program Files (x86)\Mono-3.2.3\lib\mono\4.0\Microsoft.Common.targets: error : Access to the path "C:\Dev\gitsrc\Cheese\Cheese\bin\Debug\Cheese.dll" is denied. at System.IO.File.Delete (System.String path) [0x00000] in <filename unknown>:0
at Microsoft.Build.Tasks.Copy.CopyFile (System.String source, System.String dest, Boolean create_dir) [0x00000] in <filename unknown>:0
at Microsoft.Build.Tasks.Copy.Execute () [0x00000] in <filename unknown>:0
Task "Copy" execution -- FAILED
Done building target "DeployOutputFiles" in project "C:\Dev\gitsrc\Cheese\Cheese\Cheese.csproj".-- FAILED
4.2.3 was just pushed to Stable. It happens there too.
Anything? Restarting Xamarin Studio every test run is really not practical.
Either the debugee's mono runtime is still running or XS still has the .mdb files open for calculating breakpoints (although the code appears to correctly close them).
Do you have breakpoints set? If so, what if you run the app w/o any breakpoints set? Does build afterward still cause this problem?
I want to add that this happens with MS.NET too.
No, no breakpoints. I can confirm that whenever this happens a mysterious extra 'mono' process is hanging around.
Thanks NB, that helps narrow it down a bit and is what I was thinking might be the culprit.
This was fixed a few weeks ago (although it was too late for 4.2.4)
*** Bug 19101 has been marked as a duplicate of this bug. ***
*** Bug 18540 has been marked as a duplicate of this bug. ***
I have tried to verify this issue but we are not able to build project when active runtime is mono. We have filled a separate issue for this i.e Bug 19495.
We will verify it when Bug 19495 will be Resolved.