Tag Info

New answers tagged

0

Edit: I see that the post is old, however I'll toss the answer up anyways. In my humble opinion, I think the proper way would be to design this in three pieces. Server.cs - the logic that behind the server Client.cs - the logic that behind the client Your UI. You would only need two threads, one that the UI runs on which you don't have to worry about ...


2

You can use the Mediator pattern. essentially you have a single object to which you bind events and pass that into view models rather than binding to the viewmodel event. so: public interface IMediator { void NotifyColleagues(string token, object args); void Register(string token, Action<object> callback); void Unregister(string token, ...



Top 50 recent answers are included