An Entity is a representation of data in memory. It can be a single table or multiple tables. What makes it easy is you just ask the data layer for the entity you need, without worrying about where that data is stored or how many tables are joined to get you that data.

For example, if you want invoice #43, that's what you ask for. You don't worry about joining InvoiceHeader, InvoiceDetail, Customer, Parts, Shipping, etc, tables, nor do you care that those tables were joined to get the info.

>Hi,
>
>One of the most used terms I come across in .NET world is "entity" and I admit that I am clueless about what it means. The definition of Entity in the dictionary is "something that exists as a separate thing". This is very helpful, of course <g>; they might as well simply describe it as a "thing". But back to .NET world.
>
>I was just reading an article on the web on building business objects and the term "entity" is all over there:
>"entity state"
>"entity state type"
>"entity state property"
>etc.
>
>There is also a well known framework that has he word "Entity" in it.
>
>Could someone explain to me the term "entity" in the .NET? TIA.