This may be a newbie question.
I used to just define (VB.Net for example):
dim dt as new DataTable
dataAdp.fill(dt)
But in VS.Net,
You can also right click the SQLDataAdapter1 component and click
"Generating Dataset...", after specify a name, the new xsd file will be
created as well as a correspond vb file. The VB file basically created
another class inherit DataSet class.
But in the vb code, it seems still need to do:
dataApt.fill(AutoGeneratedDataset, "SameNameOfTheTableWhenGenerating")
What's the benefit to use this function of VS.Net? I know one is you can
use the visual tool to do data binding after you have generated dataset
placed on the form designer.... Others?
I used to just define (VB.Net for example):
dim dt as new DataTable
dataAdp.fill(dt)
But in VS.Net,
You can also right click the SQLDataAdapter1 component and click
"Generating Dataset...", after specify a name, the new xsd file will be
created as well as a correspond vb file. The VB file basically created
another class inherit DataSet class.
But in the vb code, it seems still need to do:
dataApt.fill(AutoGeneratedDataset, "SameNameOfTheTableWhenGenerating")
What's the benefit to use this function of VS.Net? I know one is you can
use the visual tool to do data binding after you have generated dataset
placed on the form designer.... Others?