remoting

I have some legacy vb6 applications that need to talk to my .Net engine application. The engine provides an interface that can be connected to via .net Remoting. Now I have a stub class library that wraps all of the types that the interface exposes. The purpose of this stub is to translate my .net types into COM-friendly types. When I run this class library as a console application, it is able to connect to the engine, call various methods, and successfully return the wrapped types. The next step in the chain is to allow my VB6 application to call this COM enabled stub. This works fine for my

So I've been reading lots about interprocess communication on .Net. Named pipes, remoting. It all seems great but possibly overkill for what I need to do. I want to add a command line interface to my WPF application, so I need a simple IPC mechanism to send the string from one process to the already running app. What does SO recommend for doing so? JP Alioto NamedPipeClientStream and NamedPipeServerStream are pretty simple. Here's a pretty simple example where IPC is used to pass command line arguments from one instance of an application to another. It's not exactly what you want to do, but

I'm struggling with getting IOC to work in a remoting scenario. I have my application server set up to publish Services (SingleCall) which are configured via XML. This works just like this as we all know: RemotingConfiguration.Configure(ConfigFile, true); lets say my service looks like that (pseudocode) public class TourService : ITourService { IRepository _repository; public TourService() { _repository = new SqlServerRepository(); } } But what I rather would like to have sure looks like this: public class TourService : ITourService { IRepository _repository; public TourService(IRepository

In my ASP.NET application, I have a line in the global application start event that configures the client remoting channel by calling RemotingConfiguration.Configure(). This works well the first time, but when my web application gets recycled, the application start event is fired again causing the following remoting exception: Remoting configuration failed with the exception 'System.Runtime.Remoting.RemotingException: The channel 'tcp' is already registered. I would like to detect if the channel is already configured so that I can avoid getting this exception. Try ChannelServices

Windows does not make it possible for a 32 bit process to load a 64 bit dll, so I am trying to use remoting in order to allow the 32 bit process to interact with a 64 bit process. Here's the problem: while the two applications are located on the same machine, one is 32 bit and the other is 64 bit, and they have to be that way: making both 32 bit or 64 bit would break everything these applications are built on top of. I'm using .NET's System.Runtime.Remoting.RemotingConfiguration class and calling its Configure() method and passing a reference to an App.config file which references the

I am working on a .Net website which is going to have 1000s of concurrent users. I am thinking of keeping the business components on the app server and UI components on the web server. Database (MS SQL Server 2005) will be hosted on another server. I am planning to use the load balancing as well. Given this, what's the best way of communication from web server to app server if I want to have the optimum application performance and scalability? You can check here a performance comparison between WCF and other communication technologies (including .Net remoting). The conclusion is : WCF is

We are converting a Flex application to use some REST APIs. When adding the mx.rpc.http.HTTPService class to the code, the SWF binary output grew from 175KB to 260KB. This is an unacceptable hit. Is there any better way to do lightweight REST calls from a Flex app? Are we better off using an external interface JS just to make the calls from there? flash.net.URLLoader is built into the runtime and won't cause any increase in filesize. I've used it as a JSON client before, so you shouldn't have any troubles with it. Below is a very simple example. See documentation for HTTP_STATUS and HTTP

I am running the Akka 2.0.2 microkernel and want to implement an authentication scheme for untrusted remote actors. The first thing that comes to mind is to set up an authentication actor which returns a reference to the work actor when authentication succeeds. However, how should I protect the work actor from simply being directly looked up remotely via actorFor(), circumventing authentication altogether? That is, I want to prevent remote actors from accessing actors in my microkernel actor system without authentication. Not giving the work actor a name in actorOf() is not enough, because it