Addendum to that Ive now tried about 6 versions of project going back to 6months ago
1) It is this specific project which wont debug new projects and some other test projects set up months ago seem to debug OK. On this project cannot stop at first line of oncreate) 2) No amount of deinstalling run time/app, swapping machines works 3) Deleting Obj and bin folders doesnt work 4) Deleting suo and prefs files doesnt work 5) This rogue project throws up an interesting error in the generated r.java file saying duplicate class found but this disappears on a clean 6) Still works on an older version of MfA on the desktop so its something to do with how this project reacts to the new 4.4.41 And Im clean out of ideas From: John Murray [mailto:j...@murray.gb.com] Sent: 19 December 2012 14:20 To: 'Goncalo Oliveira'; j...@murray.gb.com; 'Discussions related to Mono for Android' Subject: RE: [mono-android] debugger breakpoints 4.4.41 Thanks for the suggestions much much appreciated However ... as you said, Ive deinstalled everything from the mobile Im testing on (two actually a Samsung Galaxy tablet running Honeycomb and a sony xperia running ICS) It also doesnt work on the emulator (Ive had situations before where i couldnt debug on the emulator so thats no big deal) Will try a restart Thanks again -keep the suggestions coming John Murray From: Goncalo Oliveira [mailto:gonc...@minkan.net] Sent: 19 December 2012 12:30 PM To: j...@murray.gb.com; Discussions related to Mono for Android Subject: Re: [mono-android] debugger breakpoints 4.4.41 John, You probably did this step already, but just in case. I also had the same problem when installing the new version. The only way I got it to work again was to clean the whole solution, uninstall shared runtime, mono framework and my application from the device and then running it again. Someone also reported that a debug restart fixed it, though it didn't for me. On 19 December 2012 11:53, John Murray <j...@murray.gb.com> wrote: Further to my last post I've now tried 4 old back up projects and none can be made to debug properly Sorry to be a complete plank but can anyone tell me the steps I need to take to de install 4.4.41 and go back to whatever was current last August? I'm getting desperate for a debuggable solution so that some work can be done over the holiday (sad I know :-( ) Tia John Murray -----Original Message----- From: John Murray [mailto:j...@murray.gb.com] Sent: 19 December 2012 11:08 To: 'Jonathan Pryor'; j...@murray.gb.com; 'Discussions related to Mono for Android' Subject: RE: [mono-android] debugger breakpoints 4.4.41 I've posted a bug For gen information A newly created project stops at breakpoints as it should I recalled that two other 'tricks' were to delete the obj and bin folders or to delete mdb and pdb files Neither of these work Obviously after each step obe cleans and builds I've imported a back up copy of the project - no luck - it took out MonoDevelop (could not see cause of crash but a message said the details had been sent to developer) After that Monodevelop is back to being an evaluation versio (see other thread on activation) so I'll have to do an offline activation again As it is something to dowith my project and its interaction with the new version any other suggestions would be welcome. Such a time waster John Murray -----Original Message----- From: Jonathan Pryor [mailto:j...@xamarin.com] Sent: 18 December 2012 20:41 To: j...@murray.gb.com; Discussions related to Mono for Android Subject: Re: [mono-android] debugger breakpoints 4.4.41 On Dec 18, 2012, at 8:09 AM, John Murray <j...@murray.gb.com> wrote: > I've had a bit of a break from my monodroid project but returned > recently - upgraded to 4.4.41 Now breakpoints are not recognised This > has happened a few times in the last couple of years on upgrades > sometimes solved simply by for example ddeleting suo file Could you please file a bug so that we can track this? Apparently a .suo file contains user options; I have no idea why this would break debugging. :-( http://msdn.microsoft.com/en-us/library/bb165909(VS.80).aspx > In this case none of the previous tricks works Do I have to completely > uninstall ? I notice someone posted in Janaury this year 2012 (with > no official response) and suggested he had to deinstall everything to > get the debugger to work > > If I have to do this is it > 1) Just an issue of reinstalling the Android-sdk > 2) Do I have to deinstall mono for Android - if so how is that done without completetely messing up the licensing (another issue) > 3) Is there something else I should be deinstalling? > 4) Does VS2010 or Monodevelop have to be deinstalled Without knowing why things are breaking, I can't say one way or the other. It doesn't make sense to me why an uninstall+reinstall would change anything... - Jon _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid -- Gonçalo Oliveira
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
