Marshalling between .NET 2.0 and 1.1?

[schaf]

Hi all!
My application (app1) is using a service via .NET Renmoting written
in .NET 1.1. Now I have converted app1 to .NET 2.0. When I start my
application app1 (now in .NET 2.0) the following exception occurrs as
soon as I subscribe my app1.object (MarshalObjectByRef) (with this
(from app1)) in the remoting object from the service.
This means, that my app1.object holds an private member to the
service.object and subscribes itself with this.

This worked fine as long as app and service are compiled in .NEt 1.1
or .NET 2.0, but if i only compile app1 in .NEt 2.0 and runs against
the service in .NEt 1.1 i get the exception below.

Is this not possible due to differences in marshalling? Or do I have
to change some settings in .NEt 2.0 (compiler settings or remoting)?

Thanks


Server stack trace:
at System.Runtime.Remoting.Messaging.Message.CoerceArg(Object
value, Type pt)
at System.Runtime.Remoting.Messaging.Message.CoerceArgs(MethodBase
mb, Object[] args, ParameterInfo[] pi)
at
System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage
msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at
System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
reqMsg, IMessage retMsg)
at
System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type)
at Service.Interface.IPublisher.Subscribe(ISessionEventSubscriber
subscriber)
at App1._Init() in...

 

[Adam Benson]

We had problems like this.

As a starting point ensure you have all the .NET 1.1 patches installed.
Go to Windows update and check.
You have to go back more than once to be sure everything's updated.

HTH,

AB
=====