On May 10, 2012, at 10:14 PM, Joshua Barker wrote:
> Why does the 4.2 alpha version of Mono.Android.dll have a publickeytoken of
> c4c4237547e4b6cd whereas previous versions had one of null?
Popular request. Many people wanted to sign their own assemblies which depended
on Mono.Android.dll and couldn't, because Mono.Android.dll wasn't signed. Now
they can.
> As far as I know, binding redirection won't allow a work around on this, so
> previous 3rd party libraries can't be used because of this.
Anything built before 4.1.2 ("4.2.0") would need a recompile anyway, because of
API breaking changes. (For example, many fields are now properties, many
parameter types and return types were changed because of enum/Color changes,
some methods were changed from non-virtual to virtual... Plus, we found
"issues" with the 4.1.2/4.2.0 installer in which it wouldn't properly upgrade
on many Windows systems, resulting in the MonoAndroidBinPath failures.)
- Jon
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
