Dataset Extended Properties (msprop:* in xsd)

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ian - 04 Apr 2006 15:13 GMT

I found reference to these in several places. First on MSDN, with
little explanation
(<http://msdn2.microsoft.com/en-US/library/8bw9ksd6(VS.80).aspx>) and
then with slightly more information
(<http://www.thechannelinsider.com/article2/0,1895,1844601,00.asp>).

As best I'm able to tell these should be governing the DataSet.xsd >
DataSet.Designer.cs creation process in the MSDataSetGenerator custom
tool. But as far as I can tell, they're not.

I'll try something as simple as this:

<xs:element name="_test1_TestDataSet" msdata:IsDataSet="true"
msdata:UseCurrentLocale="true"
msprop:Generator_UserDSName="_test2_TestDataSet"
msprop:Generator_DataSetName="_test3_TestDataSet">

and the class seems to get named _test1_TestDataSet no matter what I
do, when, according to my reading of the articles, it ought to be
_test3_TestDataSet.

Am I doing something wrong? Do I have to do something in particular to
get VS to respect these property settings? Or are these properties just
a vestige of a good thought that never made it to fruition?

Thanks,
Ian

Reply to this Message

Ian - 04 Apr 2006 20:12 GMT

A (not-so-)quick perusal of the System.Design assembly, specifically
the System.Data.Design namespace, leads me to believe that the only
accesses to these properties occur during the design phase (i.e.
parsing and writing out the XSD) and conspicuously NOT during the code
generation phase (i.e. actually WRITING the dataSet.Designer.cs file.)
The name resolution routines that get called during the assemblage of
the class file all reference the 1.1 "typedName" properties, and not
the Generator_* properties. So I guess the word on the street is "no."

Grrr.
Ian

Reply to this Message

Dataset Extended Properties (msprop:* in xsd)

Free Magazines