Is it possible to expose a remoting object on both Tcp (any port) and Http (port 80) while still running a web site from the same server?
I had this great idea (I thought) that my clients would first try to connect to the singleton object with tcp, and if that didn't work they would switch to Http on port 80. I created a virtual directory on IIS to expose it on Http and then I thought I would be able to write a small exe that would get the object from IIS and then Marshal it on a Tcp channel. But to my horror it didn't work becase all I got back was a proxy, and it seems like you can't marshal a proxy. :( So, is there any way to accomplish this? Or am I stuck with Http? Peter You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
