Michael Moreno wrote:
> Hello,
>
> I am looking for a .Net Remoting book for distributed applications with
> WinForm GUI (not for Web Services and not simple console app).
>
> Can you recommend one please?

> Michael Moreno wrote:
>> Hello,
>>
>> I am looking for a .Net Remoting book for distributed applications with
>> WinForm GUI (not for Web Services and not simple console app).
>>
>> Can you recommend one please?
>
> I found chapter 3 of the Que "MCAD/MCSD: Developing XML Web Services and
> Server Components with Visual C# .NET and the .NET Framework" by Kalani and
> Kalani to be good. David Conger's " Remoting with C# and .NET: Remote
> Objects for Distributed Applications" (Gearhead Press: In the Trenches
> Series) has also proved useful.
>
> Neither of the above was as complete as I would have liked, both have some
> errors, and the second one (Conger) uses a console application, so you may
> not like it, but taken together they got me through most of the learning I
> needed to do before striking out on my own.
>
> The main thing about remoting, I find, is that you must learn to walk before
> you start trying to run. You certainly don't want to be doing asynchronous
> remoting until you can write the various different types of synchronous
> remote calls you'll find described in the literature, with some ease and
> confidence.
>
> Both the books above contain some info on asynchronous remoting: however if
> that's where you try to start off, I think you'll find life quite difficult.
>
> Just my 2c (Dwy Geiniog Gymraeg)
>
> Peter

Michael Moreno wrote:
<snip />
> Thank you very much. For me the most important is to understand how to
> insert new .Net application and DLLs into a DCOM distributed application
> and progressively move to .Net remoting. I have done some "good" work
> already but I still cannot solve many issues such as implementing
> callbacks and to have several client or server using the same unique
> remoting interface without ending in having to create a jungle of
> TCPChannel to open.
>

"Roy Chastain" <roy@kmsys.com> wrote in message
news:39dhe1lrak2tsffhikvoulf9c4u7jfsgbb@4ax.com...
> I found Advanced .NET Remoting by Ingo Rammer (has both a C# and a VB
version of the book) to be most helpful.
> He has devoted a fair amount of pages to walking through the simple to
complex (read that to brain dead to will usually work)
> implementation of remote event callbacks. He explains why OneWay events
won't work. He also leads us away from SoapSuds etc and
> into actually writing interfaces how to minimize the amount of code that
must be shared on the local and remote systems.
>
> It is hard to get where you need to be, but it is possible.
>
> On Thu, 28 Jul 2005 09:37:13 +0100, "Michael Moreno"
<michael.ToRemove.moreno@free.fr> wrote:
>
> >> I'm no expert at asynchronous remoting, but the Kalani and Kalani book
I
> >> mentioned has 5 pages on asynchronous remoting using a delegate (which
is how
> >> it's done in .NET). The section includes an example.
> >>
> >> It's perhaps a bit extreme to buy a book for 5 pages though.
> >
> >Yes I know but I already wasted several hours on the internet to try to
> >find the solution and none of them work in real "complex" scenario.
> >
> >> What do you mean by having "several clients or servers using the same
unique
> >> remoting interface"? Are you using the term interface in its OO
meaning
> >> (i.e. a contract to provide a set of methods) - or do you mean
something
> >> else?
> >
> >Yes I use it in its OO meaning (I actually use root class that I
> >inherit from).
> >
> >something like
> >
> >class IAmAServer
> >{
> > void virtual StartMe() {}
> > void virtual StopMe() {}
> > void virtual PauseMe() {}
> >
> > void virtual RegisterClient(IAmAClient c) {}
> > void virtual UnregisterClient(IAmAClient c) {}
> >}
> >
> >All my servers (executables) must implement such an interface. The
> >clients can or cannot register to the server to get events such as some
> >platform events, status changes, Alerts, etc.
> >
> >Thank you for the references.
>
> -------------------------------------------
> Roy Chastain
> KMSYS Worldwide, Inc.
> http://www.kmsys.com

> I would advise you to look at Genuine Channels (www.genuinechannels.com). In
> the download section of there site you can find a Beginner's Guide. This is
> a very good document with complete GUI and Web sample applications. You can
> also find a number of interesting articles in there Knowladge Base section,
> concerning callbacks and events.

On Thu, 28 Jul 2005 09:37:13 +0100, "Michael Moreno" <michael.ToRemove.moreno@free.fr> wrote:

>> I'm no expert at asynchronous remoting, but the Kalani and Kalani book I
>> mentioned has 5 pages on asynchronous remoting using a delegate (which is how
>> it's done in .NET). The section includes an example.
>>
>> It's perhaps a bit extreme to buy a book for 5 pages though.
>
>Yes I know but I already wasted several hours on the internet to try to
>find the solution and none of them work in real "complex" scenario.
>
>> What do you mean by having "several clients or servers using the same unique
>> remoting interface"? Are you using the term interface in its OO meaning
>> (i.e. a contract to provide a set of methods) - or do you mean something
>> else?
>
>Yes I use it in its OO meaning (I actually use root class that I
>inherit from).
>
>something like
>
>class IAmAServer
>{
> void virtual StartMe() {}
> void virtual StopMe() {}
> void virtual PauseMe() {}
>
> void virtual RegisterClient(IAmAClient c) {}
> void virtual UnregisterClient(IAmAClient c) {}
>}
>
>All my servers (executables) must implement such an interface. The
>clients can or cannot register to the server to get events such as some
>platform events, status changes, Alerts, etc.
>
>Thank you for the references.

> I'm no expert at asynchronous remoting, but the Kalani and Kalani book I
> mentioned has 5 pages on asynchronous remoting using a delegate (which is how
> it's done in .NET). The section includes an example.
>
> It's perhaps a bit extreme to buy a book for 5 pages though.

> What do you mean by having "several clients or servers using the same unique
> remoting interface"? Are you using the term interface in its OO meaning
> (i.e. a contract to provide a set of methods) - or do you mean something
> else?