We've been using anonymous types to send our data across the wire by defining our wcf API endpoints as returning object instead of a concrete class. We have had to build a custom serializer to do this, but it allows us to have a lot of control over the response to the client without having to build classes specific to each response.
-joe On Oct 26, 2011, at 12:24 PM, Jason Meckley <[email protected]> wrote: > Maybe, but why introduce that complexity? by mapping the domain object to a > context specific dto you know if the value is present or not because it was > populated before it was sent across the wire. Not to mention the receiver > shouldn't have any knowledge of NH. > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/nhusers/-/j7FYrrN522YJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
