Why Data Contract Collection

Topics: Service Factory Modeling Edition Forum
Feb 20, 2009 at 2:34 PM
My question has to do with why to use a "Data Contract Collection" in a Data Contract Model diagram.

Is the only advantage to using a "Data Contract Collection" is that you set the "Collection Type" Property once
in the "Data Contract Collection" and then can reuse it as a Member of a Data Contract as many times as you want
without having to set the "Collection Type" for the Memebr? Also it would ensure that the "Data Contract Collection"
is of the same Collection Type evry where it is used.
e.g. Data Contract "House" has Member Rooms which is an aggregation of Data Contract Collection "Rooms"
which is a collection of Data Contract "Room"
This gives me WSDL/XSD where Rooms contain Rooms

This as opposed to just having a Memebr of a Data Contract have it's "Collection Type" property set and its "Type"
property is another "Data Contract".So that every time you want to use the collection you  have to yet
again set the "Collection Type" property in each Data Contract who has a Member that is a collection.
e.g. Data Contract "House" has Member Rooms which has properties "Collection Type" = List and "Type"=Room
and is an aggregation of Data Contract "Room"
This gives me WSDL/XSD where Rooms contain Room

So why would I want to use "Data Contract Collection"?
Are there other advantages that I am not seeing?
This is a big debeate right now in our Team on whether to NOT use "Data Contract Collection".
Any Advanteges/Disadvantages you can provide would be most helpful.
Developer
Feb 20, 2009 at 6:15 PM
Some info about DCs.
http://msdn.microsoft.com/en-us/library/aa347850.aspx
Regarding the DC Collection, can you send the diffs between the code generated using DC Collection and with DC references?
Developer
Feb 24, 2009 at 5:00 PM
See answer in thread http://www.codeplex.com/servicefactory/Thread/View.aspx?ThreadId=47895