Greetings all,
I have been playing around a bit with remoting and I have hit a bit of a snag. I have a Windows service which connects to some legacy applications. This service is an event listener. I would like to support a remote interface to allow information to be verified against the legacy system. I have all the pieces working. First, access the legacy system cannot be multi-thread. So I would setup in my service the remote class, this class when its methods are called communicates with the service's legacy connections. This work fine from within the service. However, when I try to access this remote object from via remoting, I am getting an unknown mscorlib error. If I set my remote class as a separate dll/object, I am able to successfully create the remote instance, however, this creates a second instance of the communication to the legacy systems. As long as I am testing, it is fine, but in production this will cause problems. When the remote class is contained within the webservice exe, I can not set a reference to it in the client class because only dll's can be referenced. I have tried interface definitions and all. I know my code is correct because the separate way of remoting works fine. Thanks in advance. Doug Nelson SynApp north You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
