framework 1.0 sp3 form name renaming!

[psb]

not sure if anyone still uses this, but I installed .NetFramework 1.0 sp3
(released, aug31,2004) and after that I was getting some javascript errors.

I have a user control inside a webform. basically have login.ascx inside
login.aspx. the login.ascx contains the <form> tag.

<form id="Form1" runat="server">

before the sp3 the form would render like this...

<form name="_ctl7:Form1" method="post" action="Login.aspx" id="_ctl7_Form1">

after sp3 it was this...

<form name="__aspnetForm" method="post" action="login.aspx"
id="__aspnetForm">

It is killing some of my javascript where I look for "_ctl:Form1"!

Anyone seeing this? I wonder if this same thing happens in framework 1.1
sp1 which was released same time I believe.

-Psb

 

[Karl]

At one point, microsoft introduced a bug where the form name would get
rendered with a colon in it. This isn't valid..and would cause javascript
to break (including' microsoft's own __dopostback).

I knew they had hotfixed it, didn't know the sp3 fixed it.

Anyways, since _ctl7:Form1 wasn't valid, there isn't much you can do...but
thought i'd tell you why

Karl

 

[Karl]

psb..Lew Burrus posted a thread shortly after yours called "Submit buttons
lo longer working after framework sp1"..he solved his own problem..see if
post-2 helps:

POST - 1
Turns out the required field validators were failing, no longer functional,
for reasons I could not determine. Even when I take out the RFValidator and
reinsert it, the same thing happens, the button won't
submit (though the RFValidator Text does not appear). It's sad tto find
things out like this.

POST - 2
I should have known, since sp1 for the framework is a security update....the
..js file used by the validators was not readable by the ASPNET user. I
granted read permission on its folder to ASPNET and now the validators work.

Karl

 

[Karl]

Opppss..wrong thread..

psb..Lew Burrus posted a thread shortly after yours called "Submit buttons
lo longer working after framework sp1"..he solved his own problem..see if
post-2 helps:

POST - 1
Turns out the required field validators were failing, no longer functional,
for reasons I could not determine. Even when I take out the RFValidator and
reinsert it, the same thing happens, the button won't
submit (though the RFValidator Text does not appear). It's sad tto find
things out like this.

POST - 2
I should have known, since sp1 for the framework is a security update....the
.js file used by the validators was not readable by the ASPNET user. I
granted read permission on its folder to ASPNET and now the validators work.

Karl