BinaryFormatter Version incompatibility issue?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I'm using Binary Fomatter via HTTPChannel. My remote object is hosted in IIS
5.1. I'm sure I've got both the client and sever config file correct. When I
run on localhost, all seems to work fine, but when I move the remote object
to a virtual directory on my server and attempt to run my application which
calls the remote object, I get the following error:

An unhandled exception of type
'System.Runtime.Serialization.SerializationException' occurred
Additional information: BinaryFormatter Version incompatibility. Expected
Version 1.0. Received Version 1008738336.1684104552.



I've made changes to my client config to look for the remote object on my
server. Can anyone provide me with a fix for this issue?


Regards,

Frank




.

Relevant Pages

  • Re: BinaryFormatter Version incompatibility issue?
    ... I'm sure I've got both the client and sever config file ... move the remote object to a virtual directory on my server and attempt ... An unhandled exception of type ... I've made changes to my client config to look for the remote object on ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Accessing server resources from remotable object
    ... > Your remoting host is on the IIS server, so you can have the remote object ... > write to a physical path. ... > the virtual directory and http. ... > Use a naming convention specific to each client if you are going to expect ...
    (microsoft.public.dotnet.framework.remoting)
  • Bidirectional communications with .NET remoting
    ... I have a remote object that has a public delegate. ... BinaryServerFormatterSinkProvider serverProvider = new ... My client object uses ... client-side config file is not appropriately set in the config file. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: remoting options
    ... No I did not add a reference to the remote object in my client ... I just copied it into the bin directory on my client. ... > * Create an interface dll for your remote object. ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: remoting serialization exception
    ... Is the same remote object being ... >> client and server using slightly different versions of the remote object ... > objectId, BinaryAssemblyInfo assemblyInfo, SizedArray ...
    (microsoft.public.dotnet.languages.csharp)