date:20121219

[mono-android] property getValue error (reflecting)

2012-12-19 Thread javitxin

Hi,

I have a problem when using my deveolped app..

This is the stacktrace :

+ ex {System.ArgumentException: Get Method not found for
'ID_EMPLEADO'
at System.Reflection.MonoProperty.GetValue (System.Object obj,
System.Object[] index) [0x0] in :0
at eGestionaMobile_Datos.DATOS.MONO.eGestionaTableAdapter.getCommandText
(System.Object _objeto, IList`1 propiedades, eAccion _accion, System.String
_where) [0x000ce] in D:\Proyectos
Externalia\VS2010\eGestionaMobile\eGestionaMobile_Datos\eGestionaMobile_Datos\DATOS\MONO\eGestionaTableAdapter.cs:107
} System.ArgumentException

Let me explain my architecture.

1º layer) I have an table/object layer. Each table I have to use is included
in this dll.
2º layer) I have a data engine layer to process all request. It uses the
tables(objects) from 1º layer.
3º layer) I have a business layer that interacts with UI layer and data
engine layer.
4º layer) UI layer...Layouts and activities and so on...

So, I have 3 dlls apart from my UI layer.

The error is given when my data engine layer uses an object from
table/object layer to create a command text to insert into my sqlite. It
uses reflection to get properties from the table/object and creates the
insert.

All my app goes fantastic when debugging on any device but when packaging
and installing on device it crashes...when getting the value from the
property.

May I forget some configurating when packaging it? Why works fine when
debugging it and fails when releasing app on device?

Any help please?

--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/property-getValue-error-reflecting-tp5712653.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] property getValue error (reflecting)

2012-12-19 Thread javitxin

has shared runtime anything to do with this?



--
View this message in context: 
http://mono-for-android.1047100.n5.nabble.com/property-getValue-error-reflecting-tp5712653p5712654.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] property getValue error (reflecting)

2012-12-19 Thread Goncalo Oliveira

You're getting the link shrinkage symptom... Release builds usually have
Linking set to 'Sdk assemblies'. This strips 'unused' stuff to reduce the
final package size. This can lead to reflection triggering exceptions for
not finding a type or method or property. Try building a release with
Linking set to 'None'. If the error disappears, you'll get your answer.

Check this out: http://docs.xamarin.com/android/advanced_topics/linking

On 19 December 2012 10:54, javitxin  wrote:

> has shared runtime anything to do with this?
>
>
>
> --
> View this message in context:
> http://mono-for-android.1047100.n5.nabble.com/property-getValue-error-reflecting-tp5712653p5712654.html
> Sent from the Mono for Android mailing list archive at Nabble.com.
> ___
> 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

Re: [mono-android] debugger breakpoints 4.4.41

2012-12-19 Thread John Murray

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  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

Re: [mono-android] property getValue error (reflecting)

2012-12-19 Thread Javier Martínez Sáez

Bingo!!! It worked.. but its too heavy..Any idea to reduce the final
package size?

 

Un saludo

 

Javier Martínez Sáez

Responsable Soporte Técnico eLegisla

 

  Descripción: Logo_nuevo_externalia

  www.externalia.com

Tfno.:  945 291 684 | Fax 945 205 228

sopo...@egestiona.es

 

 

  Descripción: pie_egestiona_elegisla_adr

www.egestiona.es   | www.elegisla.es
  | www.eadr.es  

 

 CLÁUSULA DE CONFIDENCIALIDAD 

Este mensaje electrónico y todos los ficheros adjuntos que contiene son
confidenciales y destinados exclusivamente para el uso de la o las personas
a las que va dirigido, pudiendo estar sujeta a Secreto Profesional. Si usted
ha recibido este mensaje por error, le agradecemos lo comunique al emisor.
Asimismo, le informamos que la distribución, copia o utilización de este
mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su
finalidad, están prohibidas por la ley.

P Antes de imprimir este e-mail piense bien si es necesario hacerlo. El
medioambiente es cosa de todos

 

 

De: monodroid-boun...@lists.ximian.com
[mailto:monodroid-boun...@lists.ximian.com] En nombre de Goncalo Oliveira
Enviado el: miércoles, 19 de diciembre de 2012 12:05
Para: Discussions related to Mono for Android
Asunto: Re: [mono-android] property getValue error (reflecting)

 

You're getting the link shrinkage symptom... Release builds usually have
Linking set to 'Sdk assemblies'. This strips 'unused' stuff to reduce the
final package size. This can lead to reflection triggering exceptions for
not finding a type or method or property. Try building a release with
Linking set to 'None'. If the error disappears, you'll get your answer.

 

Check this out: http://docs.xamarin.com/android/advanced_topics/linking

 

 

On 19 December 2012 10:54, javitxin  wrote:

has shared runtime anything to do with this?



--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/property-getValue-error-reflec
ting-tp5712653p5712654.html

Sent from the Mono for Android mailing list archive at Nabble.com.
___
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

Re: [mono-android] property getValue error (reflecting)

2012-12-19 Thread Goncalo Oliveira

That's the linker's job. But you'll have to "fool" the linker that you need
the class you're trying to do reflection with so he doesn't chop it off
from the final package.

The link I gave you shows a few examples.
I myself have created a class where I "tell" the linker that I am using a
certain class. Even though the code it's never invoked, because the linker
does this verification at compile time, the class is included.

Example here: http://pastebin.com/nqBUv2EZ
Preserves the Spidder widget as well as SelectedItemPosition property.

I know this sucks, but...
There are other methods explained in the link I gave you, maybe there is a
more suitable option for you.


2012/12/19 Javier Martínez Sáez 

> Bingo!!! It worked.. but it’s too heavy..Any idea to reduce the final
> package size?
>
> ** **
>
> *Un saludo*
>
> * *
>
> *Javier Martínez Sáez*
>
> *Responsable Soporte Técnico eLegisla*
>
> ** **
>
> [image: Descripción: Logo_nuevo_externalia] **
> **
>
> www.externalia.com
>
> Tfno.:  945 291 684 | Fax 945 205 228
>
> sopo...@egestiona.es
>
> ** **
>
> ** **
>
> [image: Descripción: pie_egestiona_elegisla_adr]
> 
>
> www.egestiona.es | www.elegisla.es | www.eadr.es
>
> ** **
>
>  CLÁUSULA DE CONFIDENCIALIDAD **
>
> Este mensaje electrónico y todos los ficheros adjuntos que contiene son
> confidenciales y destinados exclusivamente para el uso de la o las personas
> a las que va dirigido, pudiendo estar sujeta a Secreto Profesional. Si
> usted ha recibido este mensaje por error, le agradecemos lo comunique al
> emisor. Asimismo, le informamos que la distribución, copia o utilización de
> este mensaje, o de cualquier documento adjunto al mismo, cualquiera que
> fuera su finalidad, están prohibidas por la ley.
>
> *P* *Antes de imprimir este e-mail piense bien si es necesario hacerlo.
> El medioambiente es cosa de todos*
>
> ** **
>
> ** **
>
> *De:* monodroid-boun...@lists.ximian.com [mailto:
> monodroid-boun...@lists.ximian.com] *En nombre de *Goncalo Oliveira
> *Enviado el:* miércoles, 19 de diciembre de 2012 12:05
> *Para:* Discussions related to Mono for Android
> *Asunto:* Re: [mono-android] property getValue error (reflecting)
>
> ** **
>
> You're getting the link shrinkage symptom... Release builds usually have
> Linking set to 'Sdk assemblies'. This strips 'unused' stuff to reduce the
> final package size. This can lead to reflection triggering exceptions for
> not finding a type or method or property. Try building a release with
> Linking set to 'None'. If the error disappears, you'll get your answer.***
> *
>
> ** **
>
> Check this out: http://docs.xamarin.com/android/advanced_topics/linking***
> *
>
> ** **
>
> ** **
>
> On 19 December 2012 10:54, javitxin  wrote:
>
> has shared runtime anything to do with this?
>
>
>
> --
> View this message in context:
> http://mono-for-android.1047100.n5.nabble.com/property-getValue-error-reflecting-tp5712653p5712654.html
> 
>
> Sent from the Mono for Android mailing list archive at Nabble.com.
> ___
> 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
>
>


-- 
Gonçalo Oliveira
<><>___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] debugger breakpoints 4.4.41

2012-12-19 Thread John Murray

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  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

Re: [mono-android] debugger breakpoints 4.4.41

2012-12-19 Thread Goncalo Oliveira

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  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  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

[mono-android] proguard

2012-12-19 Thread Jeremy A. Kolb - ARA/NED

Is there a way to use proguard to shrink jars that's compatible with Xamarin?
___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] debugger breakpoints 4.4.41

2012-12-19 Thread John Murray

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  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  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

Re: [mono-android] debugger breakpoints 4.4.41

2012-12-19 Thread Jonathan Pryor

On Dec 19, 2012, at 6:53 AM, John Murray  wrote:
> 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?

1. Go to: https://store.xamarin.com/account/Products
2. For a given license/product, click the "Show Recent Releases" link.

The Show Recent Releases link gives download links to the .msi installer for a 
specific release. I currently see links going back to 4.2.2 from May 24 2012; 
presumably you want the 4.2.4 release.

Thanks,
 - Jon

___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] proguard

2012-12-19 Thread Jonathan Pryor

On Dec 19, 2012, at 8:52 AM, Jeremy A. Kolb - ARA/NED  wrote:
> Is there a way to use proguard to shrink jars that’s compatible with Xamarin?

I'm not sure this will ever be possible. Proguard is conceptually similar to 
our linker, and as such it requires a "global" view of all Java bytecode so 
that it knows which types and members to preserve. The problem is that it can't 
have such a global view, because the actual use is in C# code, which Proguard 
can't investigate.

This might be possible if we altered the build system so that the generated 
ACWs contained type+method references that mirrored the C# code, but any C# 
method can reference a Java type, not just ACWs, so even this idea would be 
incomplete. A "complete" solution would be a major undertaking, and we have 
many higher priority tasks to work on before even considering this...

 - Jon

___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] debugger breakpoints 4.4.41

2012-12-19 Thread John Murray

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  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  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

_

Re: [mono-android] debugger breakpoints 4.4.41

2012-12-19 Thread Jonathan Pryor

On Dec 19, 2012, at 6:33 PM, John Murray  wrote:
> Addendum to that
> I’ve now tried about 6 versions of project going back to 6months ago

Wow. Thank you.

> And I’m  clean out of ideas

Can you make an archive of that directory so that we can investigate?

One last idea: if other projects work and it's "just" this one, create a new 
project, and copy/link the files from the "bad" project into the new project, 
and see if the new project works.

I've think I've heard of other people hitting similar "bizarre" situations, and 
moving things into a new project seems to have fixed it.

 - Jon

___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

[mono-android] property getValue error (reflecting)

Re: [mono-android] property getValue error (reflecting)

Re: [mono-android] property getValue error (reflecting)

Re: [mono-android] debugger breakpoints 4.4.41

Re: [mono-android] property getValue error (reflecting)

Re: [mono-android] property getValue error (reflecting)

Re: [mono-android] debugger breakpoints 4.4.41

Re: [mono-android] debugger breakpoints 4.4.41

[mono-android] proguard

Re: [mono-android] debugger breakpoints 4.4.41

Re: [mono-android] debugger breakpoints 4.4.41

Re: [mono-android] proguard

Re: [mono-android] debugger breakpoints 4.4.41

Re: [mono-android] debugger breakpoints 4.4.41

14 matches

Site Navigation

Mail list logo

Footer information