G
Guest
I've just upgraded an asp.net project from asp.net 1.1 to 2.0. It compiles
and runs. However, on one of the pages, which worked in 1.1, it appears that
..net 2.0 goes into a perfectly good client-side vbscript onclick event and
adds a
semicolon to it. Since the event is vbscript, IE does not appreciate the
semicolon, and gives me a script error.
This application worked in asp.net 1.1 and has been working for over a year,
so it's clear that 2.0 is the source of the problem. I think .net may think
the event is supposed to be a server-side event. This only affects the
onclick event (for radio buttons)--there are several other events, such as
onkeydown, that have no problems.
Any suggestions how to get .net to stop tweaking my client-side script?
Thanks
for any ideas.
--Eachus
and runs. However, on one of the pages, which worked in 1.1, it appears that
..net 2.0 goes into a perfectly good client-side vbscript onclick event and
adds a
semicolon to it. Since the event is vbscript, IE does not appreciate the
semicolon, and gives me a script error.
This application worked in asp.net 1.1 and has been working for over a year,
so it's clear that 2.0 is the source of the problem. I think .net may think
the event is supposed to be a server-side event. This only affects the
onclick event (for radio buttons)--there are several other events, such as
onkeydown, that have no problems.
Any suggestions how to get .net to stop tweaking my client-side script?
Thanks
for any ideas.
--Eachus