Exactly as you normally would. There's no difference between implementing an
interface on a class or one decorated with the AR attribute.
From: castle-project-users@googlegroups.com
[mailto:castle-project-users@googlegroups.com] On Behalf Of Henrique Costa
Sent: 11 April 2011 05:14 PM
To:
Is it possible to wrap a DataContract using DynamicProxy and have it
serialized by just casting it to its base class?
Right now I'm getting an exception when calling a services that returns a
wrapped class but it's not clear:
{The underlying connection was closed: The connection was closed
Thank you very much! I will try that out.
Now we're at it, do you know where I can find information about the
different InspectionBehaviors? I have searched but can't really find
anything.
Regards, Asger
On Apr 8, 2:15 pm, Jason Meckley jasonmeck...@gmail.com wrote:
I believe you need to
the best advice is don't. if you need to serialize then project to a DTO.
there are numerous issues with serializing domain objects. bidirectional
relationship, internal state, NH AOP type stuff. context specific DTOs are
the perfect fit serialization.
--
You received this message because you
source code and unit tests.
--
You received this message because you are subscribed to the Google Groups
Castle Project Users group.
To post to this group, send email to castle-project-users@googlegroups.com.
To unsubscribe from this group, send email to
An entities have behavior.
There is no way to serialize that.
2011/4/12, Jason Meckley jasonmeck...@gmail.com:
the best advice is don't. if you need to serialize then project to a DTO.
there are numerous issues with serializing domain objects. bidirectional
relationship, internal state, NH AOP
Yeah but datacontracts are serialized as Xml, and only serializes its
datamembers. Im not planning to serialize the whole binary object.
On Apr 12, 2011 8:21 PM, José F. Romaniello jfromanie...@gmail.com
wrote:
An entities have behavior.
There is no way to serialize that.
2011/4/12, Jason
Dear group,
I have a requirement where-by I will have a Windows Service (running as
System) that publishes a component on net.pipe (for use by the local
machine only), but it must service multiple users logged on to the same
machine simultaneously.
It must create a 'singleton' instance per
