468,242 Members | 1,888 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,242 developers. It's quick & easy.

DataContract in separate assembly

Hi All,

In WCF, up to now, I've been using the default pattern of creating an
IService.cs that holds both [ServiceContract] and [DataContract] for the
composite types that must be returned by the service operations.

It turns out that now I want to separate my DataContract classes into a
separate assembly. I already realized that I now must reference
System.Runtime.Serialization. Do you see any problem in doing that (I mean,
placing the classes into another assembly?)

Cheers

Padu

Sep 19 '08 #1
1 4064
Padu a présenté l'énoncé suivant :
Hi All,

In WCF, up to now, I've been using the default pattern of creating an
IService.cs that holds both [ServiceContract] and [DataContract] for the
composite types that must be returned by the service operations.

It turns out that now I want to separate my DataContract classes into a
separate assembly. I already realized that I now must reference
System.Runtime.Serialization. Do you see any problem in doing that (I mean,
placing the classes into another assembly?)

Cheers

Padu
Hi Padu,

I think it's as you want. Personally, I prefer to have in a same place
(same assembly) Data and Service contracts. It's more simple to
understand the architecture.

In general, don't do things that complicate your code. Do only things
that help you.

--
Paul Musso
Sep 23 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Lauren Hines | last post: by
6 posts views Thread by Pete Davis | last post: by
6 posts views Thread by mister.mwa | last post: by
1 post views Thread by Sergei Shelukhin | last post: by
1 post views Thread by Torben Laursen | last post: by
reply views Thread by kermitthefrogpy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.