Hmm... Thanks for the answer... What I have real trouble to understand is:
Why does the (non linked) version run perfectly on the android device?
Actually I do have an 4.0.0.0 assembly. It's a service model holding data
classes (for use in a WebService) like:
using System;
using ProtoBuf;
namespace MyNamespace
{
[ProtoContract]
public class UserProfile
{
[ProtoMember(1)]
public uint Id { get; set; }
[ProtoMember(2)]
public string FirstName { get; set; }
[ProtoMember(3)]
public string LastName { get; set; }
}
}
I reference this class in a server project running on mono, in another
server project running on Windows .Net and in an android project.
If the linker just removes parts of the framework which are not used then it
should work with my application (because it runs actually on an android
device). It should just remove the parts I'm not using... That's something I
try to understand...
Beside this - what would be the best practice in the above mentioned
scenario? Should I build 2 dlls one for mono (2.0.5) and one for .Net
(4.0.0.0)? Strictly spoken I'm not sharing the same contract then anymore...
I'm serializing a class (like my UserProfile) in version 2.0.5 on one end
and try to deserialize a class in version 4.0.0.0. I expect some problems
here (thats why I was very happy that I could use my 4.0.0.0 service model
straight on any platform...). I' confused now a little bit...
Regards
Kirby
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Error-Linking-Sdk-Assemblies-tp5711774p5711788.html
Sent from the Mono for Android mailing list archive at Nabble.com.
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
