aspnetForm

[=?Utf-8?B?Um9u?=]

How do I assign a name to the form element in a master page/ child page
situation?

I have included a name= in my form declaration...asp.net always changes it
to aspnetForm. Is there a way to override that behavior and apply my own
name?

[Mark Rae [MVP]]

"Ron" <Ro*@discussions.microsoft.comwrote in message
news:BB**********************************@microsof t.com...

Is there a way to override that behavior and apply my own name?

No.

Why do you think you need to to this, AAMOI...?
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[=?Utf-8?B?Um9u?=]

I am building an application that uses a lot of Javascript. A lot of the
Javascript is adopted from another application and the form name is set.

There are numerous postbacks. Trying to reference the various elements with
all of the mangling going on is very difficult…I have eliminated all of the
controls (in favor of straight HTML), however, the use of master pages
requires the use of a runat-server form.

It is amazing to me...I don't understand why Microsoft tries to make a web
page development system look like a desktop development system. It just adds
a lot of complexity that has to be overcome if the developer does anything
that is "outside the box". I have worked with .net since before version 1.0
was released, and I have also worked with ColdFusion, PHP, and Perl. The
other development systems are a lot easier when an application comes along
that requires a lot of client side javascript.

"Mark Rae [MVP]" wrote:

"Ron" <Ro*@discussions.microsoft.comwrote in message
news:BB**********************************@microsof t.com...

Is there a way to override that behavior and apply my own name?

No.

Why do you think you need to to this, AAMOI...?
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[Mark Rae [MVP]]

"Ron" <Ro*@discussions.microsoft.comwrote in message
news:33**********************************@microsof t.com...

>>Is there a way to override that behavior and apply my own name?

No.

Why do you think you need to to this, AAMOI...?

I am building an application that uses a lot of Javascript. A lot of the
Javascript is adopted from another application and the form name is set.

There are numerous postbacks. Trying to reference the various elements
with
all of the mangling going on is very difficult…I have eliminated all of
the
controls (in favor of straight HTML), however, the use of master pages
requires the use of a runat-server form.

In ASP.NET, there can only be one server-side form (i.e. a <formelement
with the runat="server" tag), and its name will always be aspnetForm.

You don't need to specify the form container name to work with one of its
elements in client-side JavaScript.

E.g. if you have an <asp:TextBox /web control called "MyTextBox, you would
do something like:

document.getElementById('<%=MyTextBox.ClientID%>') ;

It is amazing to me...I don't understand why Microsoft tries to make a web
page development system look like a desktop development system. It just
adds
a lot of complexity that has to be overcome if the developer does anything
that is "outside the box". I have worked with .net since before version
1.0
was released, and I have also worked with ColdFusion, PHP, and Perl. The
other development systems are a lot easier when an application comes along
that requires a lot of client side javascript.

I disagree completely.
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[=?Utf-8?B?Um9u?=]

Thanks!

"Mark Rae [MVP]" wrote:

"Ron" <Ro*@discussions.microsoft.comwrote in message
news:33**********************************@microsof t.com...

>Is there a way to override that behavior and apply my own name?

No.

Why do you think you need to to this, AAMOI...?

I am building an application that uses a lot of Javascript. A lot of the
Javascript is adopted from another application and the form name is set.

There are numerous postbacks. Trying to reference the various elements
with
all of the mangling going on is very difficult…I have eliminated all of
the
controls (in favor of straight HTML), however, the use of master pages
requires the use of a runat-server form.

In ASP.NET, there can only be one server-side form (i.e. a <formelement
with the runat="server" tag), and its name will always be aspnetForm.

You don't need to specify the form container name to work with one of its
elements in client-side JavaScript.

E.g. if you have an <asp:TextBox /web control called "MyTextBox, you would
do something like:

document.getElementById('<%=MyTextBox.ClientID%>') ;

It is amazing to me...I don't understand why Microsoft tries to make a web
page development system look like a desktop development system. It just
adds
a lot of complexity that has to be overcome if the developer does anything
that is "outside the box". I have worked with .net since before version
1.0
was released, and I have also worked with ColdFusion, PHP, and Perl. The
other development systems are a lot easier when an application comes along
that requires a lot of client side javascript.

I disagree completely.
--
Mark Rae
ASP.NET MVP
http://www.markrae.net