Ok.
This is working now.
Once again, when I updated some code that used a different name, I did
not update the assembly output name (!). So I was referencing the old
dll name in my client.
I brought everything up to scratch and now I can run multiple clients
taht raise remote events ( well -- so far I'm only testing it on my
development workstation ).
Next step is to run these on separate machines.
Still -- I think remoting events is cool.
I'm not really sure why we even need all the WSE 2.0 and Indigo crap if
we've got Remoting -- which is a far more elegant technology.
ja*****@texeme.com wrote:
I set up the modified (working) ChatCentral sample code from MS.
I got it to run correctly for a single client communicating with the server.
But when I launch a second client instance it registers itself with the same
number.
If I send a message from the first client, it just shows up back on its
console, but not on the second and vice versa. They can't really 'chat'
with each other -- just the server.
Here's the code I'm using:
http://support.microsoft.com/default...b;en-us;312114