Re: C# Remoting ???
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
"Vadym Stetsyak" <vadym_s@xxxxxxx> wrote in message
news:eJzzjnVXGHA.2356@xxxxxxxxxxxxxxxxxxxxxxx
Hello, sandy82!
s> I coded a simple example in c#
s> In which their is a client and a server using a dll . I am confused on
s> the Point that u have to use the .dll on both sides .
dll has to be on both sides as it holds metainfo about types.
As you use typed var in the client and server.
If memory serves.
If you design the server side as implementing an interface. Then all the client needs is the
interface and not the class itself.
Bill
.
Relevant Pages
- Re: What doesnt lend itself to OO?
... >>server is a pure data transfer interface. ... essentially exposing the client or service implementation. ... >>paradigms can be abstracted just like any other problem space in an OO ...
(comp.object) - Re: What doesnt lend itself to OO?
... The whole idea that a subsystem is just ... > The first line exists in the server. ... objects between client and server i.e. as far as the client code is ... > external interface is the traditional input interface whose ...
(comp.object) - Re: What doesnt lend itself to OO?
... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
(comp.object) - Re: screen scrape / remote manipulation
... Functionally a dll is no different from an .exe in terms of spying ... The other option is to install software capable of monitoring TCP/IP port ... connection is established between the dll (on the client) and the server, ...
(microsoft.public.windowsxp.general) - Re: What doesnt lend itself to OO?
... >> The problem with stateless programming is that it turns object ... > server is a pure data transfer interface. ... So the client should be ...
(comp.object) |
|
