S
Shawn B.
Greetings,
We have a application that was recently migrated from ASP 1.x ==> ASP 2.0
(I'm sick of saying .NET after everything so just know that I'm talking
about .NET). We have <INPUT /> controls on the UserControl. We also have
tons of JavaScript all over the place, some hardcoded, some autogenerated
that refer to these controls when rendered.
In ASP 1.x, the HTML was rendered of the form <INPUT
name="usercontrol_inputcontrol" id="usercontrol_inputcontrol" />
But in 2, it renderes <INPUT name="usercontrol$inputcontrol"
id="usercontrol_inputcontrol" />
And all over our javascript is broken. I really don't want to change
thousands of different locations to findbyid on the name as that makes for
harder to read code and will be very timeconsuming to track all the places
down the need to be changed. Do we have any control over the rendering? Is
there a way we can make it emit the name the way it used to so that
backwards compatibility isn't sacrificed for the time being?
We've had nothing but hardships updating our web to 2.0. Took 20
programmers full-time almost 4 weeks to finally get our (1000 pages) ASP.NET
1.x application to function in 2 and even then, we still keep finding these
"little" things all over the place. Many times we almost made the decision
not to migrate to 2.0 because of the shear number of differences between 1.x
and 2.0 (ASP.NET) that need to be addressed before we can even run the
website on a staging server). Its annoying, I tell ya, annoying. And for
all that, we still may not because the migration has been so costly. We
aren't making progress on the bugfixes or other enhancements because of this
extravaganza.
Thanks,
Shawn
We have a application that was recently migrated from ASP 1.x ==> ASP 2.0
(I'm sick of saying .NET after everything so just know that I'm talking
about .NET). We have <INPUT /> controls on the UserControl. We also have
tons of JavaScript all over the place, some hardcoded, some autogenerated
that refer to these controls when rendered.
In ASP 1.x, the HTML was rendered of the form <INPUT
name="usercontrol_inputcontrol" id="usercontrol_inputcontrol" />
But in 2, it renderes <INPUT name="usercontrol$inputcontrol"
id="usercontrol_inputcontrol" />
And all over our javascript is broken. I really don't want to change
thousands of different locations to findbyid on the name as that makes for
harder to read code and will be very timeconsuming to track all the places
down the need to be changed. Do we have any control over the rendering? Is
there a way we can make it emit the name the way it used to so that
backwards compatibility isn't sacrificed for the time being?
We've had nothing but hardships updating our web to 2.0. Took 20
programmers full-time almost 4 weeks to finally get our (1000 pages) ASP.NET
1.x application to function in 2 and even then, we still keep finding these
"little" things all over the place. Many times we almost made the decision
not to migrate to 2.0 because of the shear number of differences between 1.x
and 2.0 (ASP.NET) that need to be addressed before we can even run the
website on a staging server). Its annoying, I tell ya, annoying. And for
all that, we still may not because the migration has been so costly. We
aren't making progress on the bugfixes or other enhancements because of this
extravaganza.
Thanks,
Shawn