If you have the option, and get an opportunity, I'd highly reccomend porting your asp.net webservice from WCF to WebApi 4.
WebApi 4's asp.net mvc webservices are no long WCF based, and implements REST lightweight, like it should be (there is nothing lightweight about WCF, hence the departure from it). I believe WCF is primarily intended for Enterprise Web Apps running on corporate intranets. On Wed, Oct 24, 2012 at 10:32 AM, robroysd <arjun.chan...@gmail.com> wrote: > Hi, > > I have a WCF service, embedded in an asp.net MVC3 app. I want to consume > this service thorugh my android app (mono for android). > > When i reference the service (through a shared library) i get the following > error: Error 1 The type > 'System.Runtime.Serialization.IExtensibleDataObject' > is defined in an assembly that is not referenced. You must add a reference > to assembly 'System.Runtime.Serialization, Version=4.0.0.0, > Culture=neutral, > PublicKeyToken=b77a5c561934e089'. > > I realize that the .net Profile for mono for android is different than .net > 4.0, but for the above situation, is there a work around? > > Any help is appreciated. Thanks. > > > > -- > View this message in context: > http://mono-for-android.1047100.n5.nabble.com/Consuming-WCF-4-0-Service-tp5712234.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 >
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
