I am having an issue w/ the performace of a CAO. The first method call seems
to take between 7 and 30 seconds to respond when the server and client are
on different machines. If they are on the same machine, the performance is
fine. It seems to me like the response should not take ...

we usually use IIS as appserver, but for one customer we are not allowed to
do so. For this reason we have written our own appserver to host the remote
objects. For the sake of simple configuration management it would be great
if our own appserver could use the same web.config file ...

Looking for some examples and or tutorials for remoting with vb.net.
Thanks.

I'm looking for ant tutorials or examples concerning remoting with vb.net.
Thanks

After MANY hours of frustration, I've finally gotten an object to create...
However,  I am attempting  to get a callback by using delegates at both the
server and client.
The server and the client are one in the same application, just run on

We are building a distributed application where we split the business logic,
data base and the UI (web) on three different machines. Between the web
server and the business logic server there is a firewall. For the moment we
are using web services to get data from the business layer ...

LifetimeServices seems to be killing off my SAO's and I am getting very
frustrated.
I've overridden MBR:InitializeLifetimeService() to return null for all of my
objects, but this does not solve it.

I have a system which comprises of a number of server side application
and services.  There is a thread per service or application and some
threads may also create their own application threads.
ServerApplication.exe

I am aware that .NET Remoting offers better overall performance than Web
Services, but ... is there any documentation (benchmarks) on the *magnitude*
of the performance advantage of .NET Remoting over Web Services?   By how
much is it better?

The problem:
I developed a remoting server and a corresponding client dll. I used a
dll as the remoting client because I want to prevent my applications
from knowing remoting details.

I'm currently doing priliminary research into the usability of event passing
through remoting. I've been experiencing some difficulty.
Using a sample that I found I now have the eventing working successfully
using a BinaryServerFormatterSinkProvider and a TCP Channel.

I have developed a compression sink that works with remoting using a TCP
Client and Server.  So I know that
the sink works.  I am having trouble getting this into IIS.   My client can
no longer communicate with the Remote

I possible to create a web service that launch a Windows Graphics .exe
application (like notepad.exe, for example) installed on a remote server
though a Web Service. If yes, what are the main .NET API functions involved
in the application call on the server side ?

I have created a NT Service and I expose some methods through "Remoting".
All works great. However, I want to prevent that everyone (within my
Intranet) will be able to use it.
As I understand it, assuming that the client is installed on a PC within the

I have a program that runs on multiple client pc's. Occasionally one or more
of those pc's use VPN to connect to another corporate network. When using
VPN they need to set proxy server in Internet Explorer connection settings
(proxy:8080). However, as soon as this setting is enabled ...