jb wrote:

> Uri,
>
> That's very interesting. Because I have another post elsewhere
> (http://communities2.microsoft.com/communities/newsgroups/en-us/default.aspx?pg=3&guid=&sloc=en-us&dg=microsoft.public.dotnet.framework.aspnet&fltr=)
> which is inspired by *just* what you say. I have suddenly noticed that in
> the XSD I had manually defined a unique constraint on behalf of a unique (but
> not primary) key I had in my SQL and it gets removed when I regenerate.
> Isn't that exactly what you're talking about? I'm tryinjg to find an article
> which describes precisely whatever it is that the (re-)generator does or does
> not do, so that I can take this into account --- any ideas?
>
> "Uri Dor" wrote:
>
>
>>I too wish someone could explain this annoying problem, along with the
>>fact that (re)generating dataset for a dataadapter also throws away the
>>keys I defined in the DataSet
>>
>>jb wrote:
>>
>>>Following MS' recommendation, I have changed the targetNamespace of my
>>>dataset in its .XSD file in a project I am (still) developing from the
>>>default http://www.tempuri.org to something of mine, i.e. changed the line:
>>>
>>> <xs:schema id="DataSetIC"
>>>targetNamespace="http://www.tempuri.org/DataSetIC.xsd"
>>>xmlns:mstns="http://www.tempuri.org/DataSetIC.xsd"
>>>xmlns="http://www.tempuri.org/DataSetIC.xsd" ...>
>>>
>>>Now, every time I change the database and ask Visual Studio .NET to
>>>regenerate the dataset, it chucks away my changes and resets to
>>>www.tempuri.org, which then fouls my integrations with the dataset.
>>>
>>>Is there any way I can get VS .NET to retain my target namespace change???
>>>