Click here to Skip to main content
15,890,512 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
So here is the scenario:

We are build a .NET 4.0 WPF program, build around a whole lot of WCF services. This program operates some heavy equipment (10 tonns storage elevators) and the setup is like we need to have 2 screens, with XP Embedded (sorry) , which needs to be synchronized.

We have experience with Sockets and WCF from earlier, and i know we can build a setup where we have custom classess which the client can convert to UI elements, but i do not want to do this because of all the code and the complexity that comes with that.

I want to get a custom class or list of classes pushed to the client, then in the client use this class as object for the datacontext. With this datacontext i will sett background, shape, gridlengt, visibility in addition to alot of primitive data types.
Posted
Comments
Sergey Alexandrovich Kryukov 6-Feb-14 12:03pm    
The answer is: you can share the types through WCF service, of through sockets you could use to implement some custom service with analogous features and some custom data marshaling. What is your concern?
What prevents you from developing such service, according to your requirements, whatever they are?
—SA

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900