Thanks for your reply, Alan. I realize that assembly identification and authentication is not an issue when it's all AOT compiled and statically linked etc. It's just that our existing product includes multiple strong named assembles that expose internals to each other, and I was hoping to avoid another code change for the MonoTouch version. It's not a big deal though.
Cheers. -- View this message in context: http://monotouch.2284126.n4.nabble.com/String-named-monotouch-assembly-tp4655948p4655962.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
