1

Topic: Winforms DataGridView and 2 to BindingSource

Here such here a little archaic question - to BindingSource is connected List <MyType>, and itself BindingSource is displayed through DataGridView. It is necessary to make standard CRUD over this list with a code minimum. Something examples in rumple any turbid and all conduct through . Buttons and forms. And it is necessary to manage only one , without buttons and forms. Who can that prompt?

2

Re: Winforms DataGridView and 2 to BindingSource

Hello, Northrop, you wrote: N> Here such here a little archaic question - to BindingSource is connected List <MyType>, and itself BindingSource is displayed through DataGridView. It is necessary to make standard CRUD over this list with a code minimum. Something examples in rumple any turbid and all conduct through . Buttons and forms. And it is necessary to manage only one , without buttons and forms. Who can that prompt? Can look at telerik' here, truth it paid.

3

Re: Winforms DataGridView and 2 to BindingSource

Hello, Northrop, you wrote: N> Here such here a little archaic question... It seems To me, you selected not absolutely successful decision... MS recommends to use for such scenario not List <T>, and BindingList <T>. About a difference between these classes it is possible to look here (remarkable article, by the way) the Author (: Sergey Tepljakov Data: 12/28/2008 the Primary goal of Windows applications Forms - data manipulation. At a given time application obtains the data from some source, displays to their user, the user changes given, then the changed data is located in a source (in the same or other). In some applications can not be some of the stages set forth above, but as a whole this pattern is characteristic for the majority of applications. In the application operating dataful, there is a logical correlation between level of the data and representation, we want it or not. The question in that, how many routine operation lays down on your shoulders. The data binding mechanism in Windows Forms substantially simplifies an application creation, operating dataful. The understanding of the main concepts on which the data binding is under construction, can simplify substantially creation of such applications, and also help with the decision of various problems which invariably pursue each developer., Here, here and generally it is a lot of where still. Well or, if your code receives List <T> from the outside and you can do nothing with it can write a wrapper? A class which will implement interface IBindingList. Though, I with these BindingList  also returned, in due time, to classical DataSet. Well and that? Time WinForms as a whole is considered archaic technology why and the archaic tool for operation dataful not to use? Well only DataSet it is necessary to use the typified. I even for myself on T4  typified DataSet bungled on the basis of the circuit in a XML-format. I use and do not buzz PS. By the way, concerning archaism. If the tool completely solves standing tasks and it is easier, than new, stylish, fashionable, youth and with  bows why it not to use?