Re: Serialization & versioning
From: Sam Santiago (ssantiago_at_n0spam-SoftiTechture.com)
Date: 07/30/04
- Next message: Sam Santiago: "Re: Intermittent Remoting Event Callback Problem"
- Previous message: Gil Shabat: "Re: Serialization & versioning"
- In reply to: Gil Shabat: "Re: Serialization & versioning"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 30 Jul 2004 10:21:46 -0700
I don't think so. You can create your own formatter if this is truly
desired. Check out this link:
Formatter Class (Abstract class, you must override many methods):
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemruntimeserializationformatterclasstopic.asp?frame=true
Thanks,
Sam
-- _______________________________ Sam Santiago ssantiago@n0spam-SoftiTechture.com http://www.SoftiTechture.com _______________________________ "Gil Shabat" <GilShabat@discussions.microsoft.com> wrote in message news:9510AB00-B3A0-458D-A2CC-605F17DC0387@microsoft.com... > Is there a way to tell .Net, or the formatter to ignore the version mismatch, so for instance, if I add a property only on the server object, the client may still be able to send the serialized object, but this property will be set to null on the server side? > > Thanks, > > Gil > > "Sam Santiago" wrote: > > > You could share an interface between the client and server. Check out > > section 5 of this document for details on how to share metadata between the > > client and server: > > > > Basic Remoting Task List > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconBasicRemotingTaskList.asp?frame=true > > > > Thanks, > > > > Sam > > > > -- > > _______________________________ > > Sam Santiago > > ssantiago@n0spam-SoftiTechture.com > > http://www.SoftiTechture.com > > _______________________________ > > "Gil Shabat" <Gil Shabat@discussions.microsoft.com> wrote in message > > news:B0F1EB62-C2CE-4E93-92E2-4BEF0C23CF07@microsoft.com... > > > I'm currently writing a distributed application that transfers a > > serialized object from the client to the server and back. How can I design > > the application to allow for the deployment of future releases of the > > serialized object on the server, while ensuring that old clients (those that > > still use the old serialized object) don't break? > > > > > > Thanks, > > > > > > Gil > > > > > >
- Next message: Sam Santiago: "Re: Intermittent Remoting Event Callback Problem"
- Previous message: Gil Shabat: "Re: Serialization & versioning"
- In reply to: Gil Shabat: "Re: Serialization & versioning"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|