"Michael Nemtsev" wrote:

> Hello Martin,
>
> Load assembly by name/version or filename and call AssemblyName.Version Property
>
>
> MM> Dear community,
> MM> I'm looking for a way to find out the assembly version of a remote
> MM> type.
> MM> In a .NET remoting application it's possible that the assembly
> MM> version of a
> MM> remoted type is not the same between the client and the server.
> MM> Let's say the server has the type ServerObj in a version 1.0.0.0 in
> MM> its
> MM> Server.dll assembly, but the client has an updated version 1.1.0.0
> MM> of
> MM> Server.dll at its disposal.
> MM> In the new version, ServerObj has an additional method.
> MM> As long as the client doesn't try to use the new method, things will
> MM> work like before (when both client and server were using 1.0.0.0),
> MM> but when the client uses the new method, a RemotingException is
> MM> thrown (of course - the client proxy does have the method, but the
> MM> server proxy doesn't).
> MM>
> MM> Now is there a way to find out the version the server is using? All
> MM> my trials only give me the assembly version from the client
> MM> (1.1.0.0), but I'd need the version from the server to keep the
> MM> client from using the new method.
> MM>
> MM> Is there a way without modifying the server? The application is
> MM> still using .NET 1.1 btw.
> MM>
> MM> I'd be really thankful for any suggestions...
> MM>
> MM> Regards,
> MM> Martin Müller
> ---
> WBR,
> Michael Nemtsev :: blog: http://spaces.msn.com/laflour
>
> "At times one remains faithful to a cause only because its opponents do not
> cease to be insipid." (c) Friedrich Nietzsche
>
>