We have a web project that includes some business methods called " Return to list from a list of .dll & lt;> ...
I do not remember now - it was reported that the returning collection & lt;> is better than returning the list & lt;>
Is this valid?
Note that I do not process the values returned from the BLL methods. See it in a web page
the collection & lt; T & Code> From the list list in archive list & lt; T & gt; is at least one other abstraction, but in general it is a In fact, you may want to consider returning IList . Edit: Here the collection Manufacturer, Courtesy of Reflection:
Public Collection () {this.items = New list So in reality, it wraps one layer of intangible. plus on its side is that you collection >> (which is the list While not possible & lt; T & gt; via direct or sub-clinging, because there are no interesting virtual methods in it).
The other thing is that they have the same aggregate display in the context of "o" (you believe you have default list & lt; T & gt; < / Code> use the implementation) indexer lookup will be o (1) , etc.
Comments
Post a Comment