Hi Shawn ,
I find this very similar with most 3 tier non web apps. In most
cases windows forms don't need access to the business logic, they just
need to render the data. This and remote communication requirements mean
I split my business objects into Data and Business pairs. Since the
data objects are simple Serialization is never an issue.
It also has the advantage that the front end layer is just
responsible for the GUI.
I personally prefer remoting, but it is seen here as too
complex. With Microsoft announcement that remoting is depreciated and
the lack of availability on the Compact Framework we are going more and
more to Web services ( though acting more as a remoting replacement than
presenting business services) .
The main issue I now see is that the Web Services Client in the
Gui create a copy of the Data (a proxy) . While this is fine for B2B it
is a real pain if I move some business logic into the client - as the
Server Business Logic class talks to a different type. I have hand coded
some Web Service classes (basically the same as the auto generated code,
with types substituted) my self but again is seen as too complex for
most developers and will not update as Microsoft's RAD environment
evolves. ( Note this is not my opinion) . If anyone knows how to change
this behaviour it would be appreciated.
Regards,
Ben
> -----Original Message-----
> From: Unmoderated discussion of advanced .NET topics.
[mailto:ADVANCED-
> [EMAIL PROTECTED] On Behalf Of Shawn A. Van Ness
> Sent: Friday, 19 November 2004 4:45 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [ADVANCED-DOTNET] XML public property and constructor
> serialization issues.
>
> I advise people to give up bending their business object models to
> work with XmlSerializer. The constraints are pretty heavy...
>
> http://www.windojitsu.com/blog/zenandtheartofxmlserializer.html
>
> In addition to the need for public default ctors and public visibility
> on all serializable fields, there are more subtle limitations you may
> run into, down the road -- like, losing instance-identity (eg, two
> different fields pointing to the same object) or not being able to
> serialize/deserialize an object graph.
>
> Cheers,
> -Shawn
> http://msdn.com/tabletpc
> http://windojitsu.com
>
> ===================================
> This list is hosted by DevelopMentor(r) http://www.develop.com
> Some .NET courses you may be interested in:
>
> Essential .NET: building applications and components with C#
> November 29 - December 3, in Los Angeles
> http://www.develop.com/courses/edotnet
>
> View archives and manage your subscription(s) at
> http://discuss.develop.com
===================================
This list is hosted by DevelopMentorŪ http://www.develop.com
Some .NET courses you may be interested in:
Essential .NET: building applications and components with C#
November 29 - December 3, in Los Angeles
http://www.develop.com/courses/edotnet
View archives and manage your subscription(s) at http://discuss.develop.com
