Applications written as Winforms or WPF have to have their UI elements (such as labels and textboxes) updated on the “UI Thread”.

Because “Say Something” is invoked by a non-ui thread, you have to to “marshall” the update onto the ui thread.

There are two ways to do this (as I noted in a previous comment):

One way is to put a reference to your display form in a “Shared” variable, then use the “BeginInvoke” method on the form to update the text property.

Another way is to store the “say” text in a collection, exposed as a shared variable, then use a timer on the Winform to periodically bind (read the data from) the collection if the data changes.

Hope this helps

Regards

Julian

        Dim properties As IDictionary = New Hashtable()
        properties.Add("authorizedGroup", "Users")
        properties.Add("portName", "myClient")
        properties.Add("rejectRemoteRequests", True)
        Dim ipcCh As IpcChannel
        ipcCh = New IpcChannel(properties, Nothing, Nothing)

instead of

        ipcCh = New IpcChannel("IPChannelName")

I hope this saves someone else the 2 hours of grief I had trying to get it to work.

Oh, and I also had to use

        ChannelServices.GetChannel("myClient")

instead of

        Dim ipcCh As New IpcChannel("myClient")
        ChannelServices.RegisterChannel(ipcCh, False)

on the receiving end.

Sorry if this is a naive question… I’m just getting into this… I got everything working ok, but I need multiple clients to be able to send messages to the server, but if I try sending a message from a client, whilst the server is dealing with another, I get an exception. I’ve tried setting “WellKnownObjectMode.SingleCall”, to allow an instance per client (I think!), but I still get the same error. Do I need to / can I set up a range of ports to use? Do I need to set up the client to wait until the port is free? Any help would be very gratefully accepted

It’s me again – found a solution.
Problem was that I was using windowsform – object in the “SaySomething” method.
Sure it’s just fired by the server side, but as there are two instances of the program with the windowsform – object being public, my application did it once for the form in Instance I and then for form in instance II.

If anyone needs the solution code, just mail.

Nice evening to ya all.

Great job, thank you very much!
There is just one thing I can’t deal with – if you wanna combine server and client in one program, the code in the “SaySomething” method is done twice, ain’t it?

Thanks for the help,

wos

There are a few ways to communicate between threads in this scenario.

One way is to put a reference to your display form in a “Shared” variable, then use the “BeginInvoke” method on the form to update the text property.

Another way is to store the “say” text in a collection, exposed as a shared variable, then use a timer on the Winform to periodically bind (read the data from) the collection if the data changes.

Regards

Julian

What I would like to do is use a Windows Form instead of a console app to display my values passed through the SaySomething method. When I attempt to create a Form and startup my application as a Windows Application (not a console app) I am unable to reference and modify the label on the Server form. I’ve determined the CommunicationService Class is a separate thread from the one launched through the Server form I’ve created.

Is there a way to have this SaySomething method in the Server app reference the new Windows form I’ve created?

Thanks for any help.

Steve

Dave

Simply add a reference to “System.Runtime.Remoting” and ipc remoting bliss will be yours.

Have fun!