I have a server app which hosts a remote object, published via http.
The app works fine as a self-standing .exe.
However, when I host the same code as a library .dll, the object is
unavailable to clients. I can verify that the object is indeed
published on http://localhost:8080/object1uri by viewing the location in
my browser.
However, the client reports an error : Requested service not found
(Remoting Exception)
Any issues around accessibility in in-process .dll's?
Jean-Pierre
Output from browser is as follows
System.Argument NullException: No message was deserialized prior to
calling the DispatchChannel Sink. Parameter name: requestMsg at
System.Runtime. Remoting.Channe ls.DispatchChan nelSink.Process Message(ISer
verChannelSinkS tack sinkStack, IMessage requestMsg, ITransportHeade rs
requestHeaders, Stream requestStream, IMessage& responseMsg,
ITransportHeade rs& responseHeaders , Stream& responseStream) at
System.Runtime. Remoting.Channe ls.BinaryServer FormatterSink.P rocessMessag
e(IServerChanne lSinkStack sinkStack, IMessage requestMsg,
ITransportHeade rs requestHeaders, Stream requestStream, IMessage&
responseMsg, ITransportHeade rs& responseHeaders , Stream& responseStream)
at
System.Runtime. Remoting.Channe ls.SoapServerFo rmatterSink.Pro cessMessage(
IServerChannelS inkStack sinkStack, IMessage requestMsg,
ITransportHeade rs requestHeaders, Stream requestStream, IMessage&
responseMsg, ITransportHeade rs& responseHeaders , Stream& responseStream)
at
System.Runtime. Remoting.Metada taServices.SdlC hannelSink.Proc essMessage(I
ServerChannelSi nkStack sinkStack, IMessage requestMsg, ITransportHeade rs
requestHeaders, Stream requestStream, IMessage& responseMsg,
ITransportHeade rs& responseHeaders , Stream& responseStream) at
System.Runtime. Remoting.Channe ls.Http.HttpSer verTransportSin k.ServiceReq
uest(Object state) at
System.Runtime. Remoting.Channe ls.SocketHandle r.ProcessReques tNow()
*** Sent via Developersdex http://www.developersdex.com ***