targetSchema - Netscape Buttons wont work

I am creating a new web site and this one is for all browsers.

The targetSchema is Navigator 4.0.

I have created a button and placed some code behind, something I have done a thousand times.

Why then won't the code work in this targetSchema when the button is clicked?

Thanks,

Zathnevermind, I had some text boxes on a control on that form and the button was trying to validate them... DOH

TargetSchema meta tag and TargetSchema attribute

When creating a new .aspx page, VisualStudio creates a meta tag called"vs_targetSchema" that holds the following value:"http://schemas.microsoft.com/intellisense/ie5". When creating a new.ascx page, VisualStudio create a "TargetSchema" attribute within the@dotnet.itags.org.Control directive which holds this same value.
If I'm building an application that I want to be browser-independant,should I eliminate this meta tag and attribute, should I add additionalmeta tags and attributes, or will any of these actions make adifference?
Thanks in advance for your help!
Hi there,
Just add following in your web.config file.. This should do the job for you.
<browserCaps>
tagwriter=System.Web.UI.HtmlTextWriter
</browserCaps>
Regards,

Thanks a lot for your reply ... I'm going to read up on browerCaps.

However, I'd still like specific information concerning my questions about the TargetSchema metatag and @.Control attribute. I'd appreciate any help.

Thanks again.

targetSchema gets reset

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?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?
>
Uri,
That's very interesting. Because I have another post elsewhere
(http://communities2.microsoft.com/c...rk.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 (bu
t
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 articl
e
which describes precisely whatever it is that the (re-)generator does or doe
s
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:
>
Uri,
That's very interesting. Because I have another post elsewhere
(http://communities2.microsoft.com/c...rk.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 (bu
t
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 articl
e
which describes precisely whatever it is that the (re-)generator does or doe
s
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:
>
I believe we're talking about the same thing. Regarding the article -
haven't seen such an article yet.
jb wrote:
> Uri,
> That's very interesting. Because I have another post elsewhere
> (http://communities2.microsoft.com/c...rk.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 arti
cle
> which describes precisely whatever it is that the (re-)generator does or d
oes
> not do, so that I can take this into account -- any ideas?
> "Uri Dor" wrote:
>

targetSchema gets reset

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?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?
Uri,

That's very interesting. Because I have another post elsewhere
(http://communities2.microsoft.com/c...rk.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?
Uri,

That's very interesting. Because I have another post elsewhere
(http://communities2.microsoft.com/c...rk.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?
I believe we're talking about the same thing. Regarding the article -
haven't seen such an article yet.

jb wrote:

> Uri,
> That's very interesting. Because I have another post elsewhere
> (http://communities2.microsoft.com/c...rk.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?
>>>
>>