Hi Jon, I fixed the issue of missing dll's ect.
For code sharing however.. facing issues. To simply the scenario, here's the deal: Project A is a normal .NET class library. This project contains a WCF Reference, to make common calls through file somefile.cs which uses WCF. Project B is an Android Class Library (mono for android profile) This project adds "as a link" somefile.cs from project A There is no way no matter what i tried, that the "as a link" file added in project B, resolves the wcf reference. Adding as a link, just does not work in this case when WCF reference is involved. Project B want's its own WCF reference. Couldn't get around this. So i've done the following: New Project A (previously project B) now has WCF reference, uses it and makes calls New Project B (Android App) references Project A, and uses the calls. With this approach, i guess if i build iOS, WP7 apps, i'd have to add WCF references to those projects, and use it. what im thinking is, Since all code only uses WCF, i only have to maintain a consistent server side WCF. Client projects (Android,iOS,WP7) can add new functionality as WCF references, and use it. I realize that you answered my question, and thanks for that. But in the above case, i tried things but didnt work. If you have any suggestions, let me know. Thank you. -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/Consuming-WCF-4-0-Service-tp5712234p5712261.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
