Re: [ADVANCED-DOTNET] Interface-based Remoting and GAC'ed Assemblies

Interestingly, Mono implemented WellKnownClientTypeEntry differently, and may not have the same issue: From [1] public WellKnownClientTypeEntry (Type type, string objectUrl ) { AssemblyName = type.Assembly.FullName; TypeName = type.FullName; obj_typ

Re: [ADVANCED-DOTNET] Interface-based Remoting and GAC'ed Assemblies

Oops! Copying and pasting from Reflector into an email didn't quite work as well as I thought. Here's the email again, without all the html goo. Allright, I think I found the answer to my issue, with some help from Reflector. The issue seems to be in the constructor of the System.Runtime.Remot

Re: [ADVANCED-DOTNET] Interface-based Remoting and GAC'ed Assemblies

Allright, I think I found the answer to my issue, with some help from Reflector. The issue seems to be in the constructor of the System.Runtime.Remoting.WellKnownClientTypeEntry class: public *WellKnownClientTypeEntry*(Type type, string

Re: [ADVANCED-DOTNET] Interface-based Remoting and GAC'ed Assemblies

I don't think that's it, actually. I think it has to do with the client-side remoting configuration, instead. I did try what you suggested, though. In my case the RemotingServiceImpl class was defined in a Windows Service executable. So, I refactored it out into a library assembly that was stro

Re: [ADVANCED-DOTNET] Interface-based Remoting and GAC'ed Assemblies

You need to fully qualify the aseumbly name in the wellknown element type="MyNamespace.RemotingServiceImpl, RemotingService, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1243fac112c" > objectUri="RemotingService.rem" /> Regards Richard Blewett - DevelopMentor http://www.dotnetconsult.c