ASP.NET enterprise architecture: business layer
<p>I'm an ASP.NET/C# developer and I've been working on this area for two years. I recently entered in a new ASP.NET project where the guy who created the enterprise architecture is quite absent. Because of this situation I'm trying to understand pros and cons of some unusual decision.</p>

<p>Most of all, I noticed that he created a business layer where every object is, at real time, a collection of object. </p>

<pre><code>public class User : List &lt; User &gt; {}
</code></pre>

<p>Even I know that I should ask these questions to the one who created this structured, but i'd like to know if someone could tell me the pros of defining an object as collection in business layer.</p>
