DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: 15 Mar 2007 08:05:26 -0700,    posted on: microsoft.public.dotnet.myservices        back       

Thread Index
  1    Abbas


Changing return object without blowing up old clients   
Hi,

I have a web service that returns an object, call it myReturn, which
contains information regarding payments, etc....  I have a new
specification, to add a new property to myReturn to handle some extra
calculations (ie. for amortization).  However, I have existing clients
with proxies based on the old object definition.  How can I make sure
that adding this extra data being sent back doesnt cause the old
clients to blow up?

I can provide some code samples if that would help.

Thanks,

Ammar
Date:15 Mar 2007 08:05:26 -0700   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us