I have based my application on the "VB.NET How-To: Remoting" sample code.  I
copied the Customer client and server, and created one which stored some
credentials in an ArrayList.  The Customer client was retained in the code,
and still works. However, the new Credentials client acts ...

My client is in a DMZ trying to connect to a asp.net hosted remoting
app.  Inside the firewall it works and my client has this config file:
            <client url="https://servername/test/HelloWorldObject3"
displayName="MyApplication">

I'm developping a distributed application where a client app calls some
methods on a remote .NET remoting object. For some reasons, i have to host
that object within a Windows service (not IIS) using a TCP channel  and i
can therefore not use the authentification features of IIS ...

I have a web service that adds a DIME attachment:
[WebMethod]
public void GetFile(string filename)
{

I've been skimming several articles about Remoting.  I know remoting is the
best fit for our needs (no firewall, .NET on both ends, etc.), but I can't
figure out if I should use client-activated objects or SingleCall objects.
I've read that client-activated is the most similar to ...

I haven't dug very far into remoting yet and I'm wondering if Remoting as
the same features as COM+ (queuing, pooling, transactions) or is Remoting a
whole different distributed computing animal separate from what COM+ tries
to achieve?

I have a problem bothering me for a few days.
I have a distributed application working very well on .Net Framework 1.0
(IIS hosted) for a while. But, now I got an issue to transfer it to
Framework 1.1 because new IIS 6.0 doesn't support Framework 1.0 within new

I am writing a client-server application with .NET
Remoting and everything was working fine until I
introduced the System.Drawing namespace into my dll
component. Now when I try to run soapsuds.exe to generate

I want to pass an object by ref to a method of a server
activated object, but keep getting the error:
"Because of security restrictions, the type
System.Runtime.Remoting.ObjRef cannot be accessed"

I am looking for a way to create a custom exception.  What I have does not
seem to work.  I hope someone can either tell me how to do it or what I am
doing wrong.
I have a Remote process that works really well.  So I created another dll,

I have heard that .NET Remoting is going away in favor of Web Services.  Is
this true?  If so, what's happening in the Web Services world that can help
make transmission of text packets more efficient?
Thanks,

Sorry for too much text to read but I am sure you all faced the same or
simillar problem during the course of developing the remoting applications.
So, please continue...it will be interesting.
I am developing a set of application using remoting architecture. After

I have an assembly that contains several classes that are used by a
Windows Service application.  Each class inherits from a base class
that provides the capability to log events to a file.  The base class
uses a shared method to write to a single log file.  The service app

Hello!
I have considered .NET Remoting as an alternative to
Sockets in this way:
I want clients to send files to a server

I have a Windows Forms application that instantiates an instance of another
class that implements a remoting server.  Using SAO, with Singleton mode,
another Windows Forms application, on the same computer, acts as a remoting
client, and calls a method in the remoting server class, ...