On May 16, 2012, at 1:11 PM, Stuart Lodge wrote:
> Important note: the code below loads PCL libraries, but I can also reproduce
> this on non-PCL code if required - the project I first reported the problem
> on was "normal monodroid-only code".
This seems odd:
> 05-16 16:57:34.910 D/Mono ( 6484): Assembly Loader probing location:
> '/data/data/com.cirrious.twittersearch/files/.__override__/System.Windows.dll'.
Why is System.Windows.dll present? Where are you getting System.Windows.dll
from?
Moving on...
> 05-16 16:57:34.915 D/Mono ( 6484): Assembly Loader probing location:
> '/Users/builder/data/lanes/monodroid-mac-4.2-series/bb1beee2/source/monodroid/builds/install/mono-armv7/lib/Cirrious.MvvmCross.Plugins.Json.dll'.
This is very odd. For all the preceding assembly loads, it looks in the
.__override__ directory first, e.g.:
> 05-16 16:57:34.910 D/Mono ( 6484): Assembly Loader probing location:
> '/data/data/com.cirrious.twittersearch/files/.__override__/System.Windows.dll'.
The fact that it's probing for
/Users/builder/data/lanes/monodroid-mac-4.2-series/bb1beee2/source/monodroid/builds/install/mono-armv7/lib
suggests that it doesn't exist in the .__override__ directory.
Does Cirrious.MvvmCross.Plugins.Json.dll exist on the device?
adb shell ls -l
/data/data/com.cirrious.twittersearch/files/.__override__
If Cirrious.MvvmCross.Plugins.Json.dll isn't there, that's the problem; it
needs to be part of your Application project references.
What's odd is that Cirrious.MvvmCross.Plugins.Json.dll is included in your
.apk. I'm not sure why it would be found by .apk generation but not fast
deployment... :-/
- Jon
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
