DataSet Change Regeneration

  • Thread starter Thread starter Chuck Cobb
  • Start date Start date
C

Chuck Cobb

I have a dataset schema in an XSD file. I changed one of the primary key
constraints in the XML to add a second column to a key that formerly only
had one column. The change shows up fine in the DataSet.XSD file both the
graphic and the XML, but the DataSet.VB file does not get regenerated with
the change.

How do I force VS.Net to regenerate the VB Code associated with the dataset?

Thanks,

Chuck
 
I think I've partially figured out the answer to this. The way to force
regeneration of a dataset is to go to the graphic view, right-click on the
background and then select "Generate DataSet", that will force VS.Net to
regenerate the VB dataset definitions.

What I'm having a problem with now is that it seems to choose a different
file to create them in. My old file was named xxDataSet.VB and the new one
is named xxDataSet1.VB. It seems to have lost the connection to the
original dataset definition and wants to create a new one now. I'm still
struggling with how to tell it to use the original dataset definition file
and not create a new one.

Has anyone else experienced this problem?

Thanks,

Chuck
 
Hi Chuck.

Hmm...not sure about that; but a different namespace for the DS class is generated if the DA generates the DS...

If the schema-designer is generating the DS class then don't re-generate it with the DA...

[BTW, VS does a nice job of updating an existing DS with changes in the
schema-Designer: a DS is updated every time the XML-Schema is saved, if, as
you said, "Generate DataSet" is selected in schema-designer... ]

Derek LaZard
 
Back
Top