Weird Bug with Redirects

[FeatureRich]

I have a very simple page. On load, it populates a drop down list.
Once something is selected and a continue button is pressed, the data
value of the selection is appended to a url as a query string and then
the user is redirected to the new URL. Here is my problem..

Suspect code
Private Sub btnContinue_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles btnContinue.Click
Response.Redirect("page2.aspx?state=" & ddlStateSelect.SelectedValue)
End Sub

With the project running local, in IE6 on my machine - everything
works.
With the project running on a test W3K server built in release mode -
the postback happens but no redirect.
With the project running on a test W3K server built in release mode,
running a FireFox browser - everything works.
With the project running on a test W3K server built in debug mode and
run through VS.Net debugging - everything works.

What gives? On IE6 with a release build the button click causes the
page to be refreshed but the redirect is never called. It is the only
line of code in the click event handler and the load is working fine.
Any ideas? Once more, why would the exact same run work in other
browsers but not IE?

Thanks

 

[Alvin Bruney [MVP]]

the problem is most likely that your event handlers became unmapped in the
release version. Rebuild the project AFTER remapping the handler

 

[FeatureRich]

the problem is most likely that your event handlers became unmapped in the
release version. Rebuild the project AFTER remapping the handler

--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok

I have a very simple page. On load, it populates a drop down list.
Once something is selected and a continue button is pressed, the data
value of the selection is appended to a url as a query string and then
the user is redirected to the new URL. Here is my problem..

Suspect code
Private Sub btnContinue_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles btnContinue.Click
Response.Redirect("page2.aspx?state=" & ddlStateSelect.SelectedValue)
End Sub

With the project running local, in IE6 on my machine - everything
works.
With the project running on a test W3K server built in release mode -
the postback happens but no redirect.
With the project running on a test W3K server built in release mode,
running a FireFox browser - everything works.
With the project running on a test W3K server built in debug mode and
run through VS.Net debugging - everything works.

What gives? On IE6 with a release build the button click causes the
page to be refreshed but the redirect is never called. It is the only
line of code in the click event handler and the load is working fine.
Any ideas? Once more, why would the exact same run work in other
browsers but not IE?

Thanks

That is exactly what it appears like happens. But I still dont
understand the inconsistent behavior between browsers. It would seem
that if the handlers were borked that it wouldnt work across browsers.

Found another interesting piece of info, my front end guy who normally
handles all the html and graphics stuff had placed a old style SSI in
the aspx page that links in another small aspx page that has server
side code to mess with a cookie. Could this injection of dynamic code
in a otherwise codebehind based app cause this sort of inconsistent
behavior? But even so, why on some browsers and not on others?

Thanks again for the help with this tricky problem.

 

[Alvin Bruney [MVP]]

yes, injection can cause the unmap. As for the other question regarding why
on some browsers - I have no clue.

--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok

the problem is most likely that your event handlers became unmapped in
the
release version. Rebuild the project AFTER remapping the handler

--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok

I have a very simple page. On load, it populates a drop down list.
Once something is selected and a continue button is pressed, the data
value of the selection is appended to a url as a query string and then
the user is redirected to the new URL. Here is my problem..

Suspect code
Private Sub btnContinue_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles btnContinue.Click
Response.Redirect("page2.aspx?state=" & ddlStateSelect.SelectedValue)
End Sub

With the project running local, in IE6 on my machine - everything
works.
With the project running on a test W3K server built in release mode -
the postback happens but no redirect.
With the project running on a test W3K server built in release mode,
running a FireFox browser - everything works.
With the project running on a test W3K server built in debug mode and
run through VS.Net debugging - everything works.

What gives? On IE6 with a release build the button click causes the
page to be refreshed but the redirect is never called. It is the only
line of code in the click event handler and the load is working fine.
Any ideas? Once more, why would the exact same run work in other
browsers but not IE?

Thanks

That is exactly what it appears like happens. But I still dont
understand the inconsistent behavior between browsers. It would seem
that if the handlers were borked that it wouldnt work across browsers.

Found another interesting piece of info, my front end guy who normally
handles all the html and graphics stuff had placed a old style SSI in
the aspx page that links in another small aspx page that has server
side code to mess with a cookie. Could this injection of dynamic code
in a otherwise codebehind based app cause this sort of inconsistent
behavior? But even so, why on some browsers and not on others?

Thanks again for the help with this tricky problem.