OK I can think of another reason. You were depending on our bug: MfA had
been doing completely wrong thing, which was fixed in 4.2.5 It must not
have collected resources and assets from all the assemblies into a
directory. It resulted in unexpected overwritten resources and assets.
As in my previous explanation, pure Java Android library project never
supported assets bundled in a library, and our Android library project
support depends on Android's aapt. As long as aapt does not accept them,
it cannot be supported in MfA.
You might want to open an issue to Android Open Source Project for this
feature request.
code.google.com/p/android/issues/
Thanks,
Atsushi Eno
tsukrov wrote:
It was working with xam 4.2.3, previous Android SDK.
This bin/res & bin/assets approach.
I'm not able to reinstall 4.2.3 at the moment, but absolutely sure, it was
working.
The only reason to use assets were ttf-fonts.
It's impossible to instantiate them from a resource and I don't want to
create files on start.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/4-2-5-resources-party-stopper-tp5711078p5711169.html
Sent from the Mono for Android mailing list archive at Nabble.com.
_______________________________________________
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
