Any advantages of binding a list of objects to a grid instead of to a datatable? (.NET) -


I have a business object, we call a customer. I have a DAL method which brings back a datalet to customers. I have a UI that has a grid that will display a list of customers.

My question is .. Is it ok to bind the grid to the dataset, which means that the UI will have a reference for the system, the data or the dataset should first be converted to an ILID and the grid Should bind? Conversions in a list from DT can be a performance hit, and I do not see that I am getting the data instead of going directly with the data using it. Plus, I love to count worthy viewer!

What are the real benefits of using the list of items rather than data data?

In addition to architecture to use a list of objects on a statistic, only real The advantage is that you can find strongly typed assets (which you can get with the dataset you typed). But if you are databanking that does not really give much importance.

It is perfectly ok to share the figures, and in fact, very good applications are used because their architecture They will pull the datatable back from the DAL instead of the objects. I personally do not do this, but there is nothing wrong in it.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -