Server.Transfer Does Not Invoke IsPostBack in .NET Framework 1.1

G

Guest

Hello,

Quick question and I would really appreciate if anybody could helps me.
Here are the steps to reproduce the problem. Create simple ASP.Net
application. In code behind added protected class variable:

protected string _result = "No result";

Page Load event has:

if (IsPostBack)
_result = "Posted back";
else
_result = "Loaded";

Form has the following code:

<html>
<head>
<title>WebForm1</title>
<meta name="GENERATOR" Content="Microsoft Visual Studio .NET 7.1">
<meta name="CODE_LANGUAGE" Content="C#">
<meta name=vs_defaultClientScript content="JavaScript">
<meta name=vs_targetSchema
content="http://schemas.microsoft.com/intellisense/ie5">
</head>
<body MS_POSITIONING="GridLayout">
<Form method="POST" name="ScheduleApptForm" id="ScheduleApptForm"
runat="server">
This is Test Control display content!!!! Result : <%=_result%>
<br>
<asp:Button class="ScheduleApptFormSubmit" id="_btnSend"
runat="server" Height="21" text="Schedule Your Appointment"
TabIndex="18"></asp:Button></TD>
</Form>
</body>
</html>

Everything works fine until I have added in Global, Application_BeginRequest
following code:

Server.Transfer("WebForm1.aspx"); // or any other form name. Just trying to
transfer form to itself.

And that’s it. IsPostBack returns incorrect value. This issue definitely the
one mentioned in
http://support.microsoft.com/default.aspx?scid=kb;EN-US;821758 and should be
fixed two years ago. I have reinstalled Microsoft .NET Framework 1.1 Service
Pack 1. It doesn’t help. Any idea or suggestion of what I did wrong? Does it
mean that Service Pack installed incorectly?

Regards,
Alex.
 
G

Guest

Hello Nathan,

Thanks for the replay :). I know what Server.Transfer does and what
Response.Redirect does. I don’t need to redirect my request to new URL (by
301, 302 or any other reason). I just want the different pages handle
different requests based on parameters on SERVER SIDE. Client (browser)
should not be aware of this internal process. (I.E. supporting such
functionality as ‘skins’ as so on). But any way, my question is not why I
have to use Server.Transfer. The question is why IsPostBack is not
initialized correctly after Server.Transfer call, but should be accordingly
to 'http://support.microsoft.com/default.aspx?scid=kb;EN-US;821758'.
By the way I have reinstalled Microsoft .NET Framework 1.1 Service Pack 1
twise. (that hot fix is included in Servise Pack)

Thanks for the attempt to help.

Regards,
Alex.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,484
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top