Personally I think it is wrong as your coupling your client application to the serverside objects. Which mean you always have to change both even when the...

Even with this model then your dtos become the bottleneck when it comes to changing them. There's always something you need to share between the client and the...

For Example Lets take VAT(uk tax), in your domain object the calculation is: public decimal VAT { get { return Price * 17.5%; } } In your DTO it's just a...

I've been stuck with this way of sharing data a lot lately, since we have a service whose outputs vary quite often, and we try to limit spreading its output...

Hi Simone Do you have an example? Cheers Andy ... -- ================= I-nnovate Software - Bespoke Software Development, uk wirral. http://www.i-nnovate.net...

Online store product page. Product data is supplied by a service and several clients consume it, the principal being the store web page. Data structure changes...

Hmm The only thing I can think of is to return xml, then the clients can parse it however they want. Maybe something along the lines of all common data is ...

Exchanging xml is how it's been done until recently, and initially we thought that providing a strongly typed contract to the client would be a big step...

XML rarely makes a lot of sense as a way to work with data. It is great for storage and transfer of data, but it isn't nearly as nice to work with as objects....

Thank you guys for your time, but let us stop discussing the XML approach in this thread (feel free to fork with another subject). As I stated before, I don't...

Sorry for bringing the discussion out of topic, although the problem I described is exactly as I read in the title, sharing (value) objects between (onion ;) )...

Simone, my mistake was to mention the client in my question. Let's focus on the server: it has a domain layer and an application layer. Now the domain layer...

I'll post on this soon... But I personally don't like Enums too much. You can't attach behavior to them, so you wind up with stuff like this: switch...

... behavior to ... treated ... Yeah I agree but they can be very useful, I end up quite often using an enum (presented to the outside world) and a type safe...

... I commonly start with a enum and then refactor to a class when I need to. Here's a simplified example. Original enum: enum Op { None, All, ... } Refactored...

I just described the same. I'm actually ok with sharing DTO's between the client and the server. The problem is yet on the server. I asked whether it is...

By exposing your domain layer, even with value objects, you still might be exposing behavior you didn't want to. Value objects are still a destination for...

What do you mean by enum classes? If I have, for example, an entity Patient which has an enum property Gender. Do you propose Gender to be a class instead of...