wcf data services - Connecting MVVMCross Portable connect to WCF DataService. Is it possible? -



wcf data services - Connecting MVVMCross Portable connect to WCF DataService. Is it possible? -

i need advice people. writing engineering science work project in vs2012 used auto dealership. have sql database, wcf dataservice, wpf application (which connected succesfuly wcf) , wanted create mobile version too. chose mvvmcross portable create mono android , wp7 app 1 core. , have problems here connecting wcf dataservice mobile portable core like:

unable add together service reference specified odata feed because wcf info services not installed target framework. install supported version of wcf info services, see http://go.microsoft.com/fwlink/?linkid=253653.

i searched on net , seems portable class library doesn't back upwards wcf info service yet. writing question in hope there solution this. if not shall wait?

or perhaps need alter wcf info service normal wcf service work on mvvmcross portable there lot of work alter in app have in wpf done,

or maybe should mvvmcross master, without portable-class-library, there no back upwards android connect info service.

i read little simply.odata have no thought how set work succesfuly.

thanks in advance.

i've connected mvvmcross applications wcf basic http info services of droid, touch , winphone (never tried winrt or wpf - should work too)

you are, however, right wcf code need different on different platforms - because code wcf uses isn't portable.

i think there 2 basic choices how tackle this:

wrap wcf code behind portable interface - interface deals in portable dto classes , presents interface get/send. you'll need write little class each platform maps portable dto's to/from non-portable ones. tools automapper may help - haven't tried on monodroid or winphone though.

use file-linking in core , maintain separate library projects each platform. illustration of file linking approach take @ https://github.com/redth/wshlst/ - azure mobile services rather wcf - same principals apply.

neither of these 2 approaches perfect - both set overhead development - both still provide way share code , build app moving forwards.

i prefer approach 1 - provides clean interface separating current network stack app logic - , provides me technical route removing wcf , replacing webapi or service stack in future.

in near future, there may shared portable class library profile supports wcf functionality across monotouch , monodroid - uncertainty available @ point on wp or winrt :/

i'm afraid don't know simple.odata (this https://github.com/simplefx/simple.odata) - trust guys wrote lot, don't know how dynamic code works on wp , monodroid. believe should work on both - there may issues code relies on reflection.emit.

one final point - whenever network related on wp, seek enable gzip compression if can - wp doesn't provide default.

wcf-data-services mvvmcross portable-class-library

Comments

Popular posts from this blog

javascript - mongodb won't find my schema method in nested container -

Hibernate criteria by a list of natural ids -

ios - Lagging ScrollView with UIWebview inside -