Have run out of time for today... But what I think the problem is any file which is not directly referenced.
e.g. TwitterSearch referenced Cirrious.MvvmCross.Droid which referenced Cirrious.MvvmCross.Json By referencing Cirrious.MvvmCross.Json directly from TwitterSearch then the process failed on the next file along (NewtonSoft.Json) instead If it helps, this was building in the previous version (including the 4.2 alpha) More to follow Stuart On 16 May 2012 20:39, Stuart Lodge <[email protected]> wrote: > I knew it was a mistake sending you the trace from the PCL version.... > > Before I get distracted, please remember that I'm seeing the problem in > non-PCL code too :) > > Now the distraction: > > For the explanation on System.Windows.dll, this is the way that I've > gotten PCLv2 Profile104 libraries to run inside MonoDroid. Basically I have > added two shim DLLs to my MonoDroid projects which do the necessary type > forwarding and/or type declaration for: > - System.Net - all types forward to monodroid's System.dll - see > https://github.com/slodge/MvvmCross/tree/vnext/Cirrious/System.Net > - System.Windows. - a few types declared (e.g. ICommand) and a few > forwarded (e.g. ObservableCollection) - see > https://github.com/slodge/MvvmCross/tree/vnext/Cirrious/System.Windows > > Slightly longer explanation on > http://slodge.blogspot.co.uk/2012/05/portable-class-libraries-in-mvvmcross.html > and > http://slodge.blogspot.co.uk/2012/04/using-portable-library-tools-for.html > > > > > > > Now I'll go look at the Json problem - thanks for the help :) > > > On 16 May 2012 18:40, Jonathan Pryor <[email protected]> wrote: > >> 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 >> [email protected] >> >> UNSUBSCRIBE INFORMATION: >> http://lists.ximian.com/mailman/listinfo/monodroid >> >> >
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
