Wrox Home  
Search P2P Archive for: Go

  Return to Index  

aspx_professional thread: Server.Transfer Issue


Message #1 by "Debreceni, David" <david_debreceni@r...> on Wed, 14 Aug 2002 11:59:31 -0400
Thanks for the response.  I tried the page.response.clear and the
page.response.clearcontent, but they did not work.  All the content was
there still.  I tried putting these in the page_load of the page I am
transferring to, and also right before the server.transfer statement in the
catch, neither of which worked.  As for the document.write, where would that
be?  Just in the top of the page that I am transferring to?

 
 
David Debreceni
Senior VB/ASP Developer
David_Debreceni@r... <mailto:David_Debreceni@r...> 
xxx-xxx-xxxx  x1086


-----Original Message-----
From: Albert Davis [mailto:albertdavis@h...]
Sent: Wednesday, August 14, 2002 1:35 PM
To: ASPX_Professional
Subject: [aspx_professional] Re: Server.Transfer Issue


On the client-side of things you can use Document.Write(""); to flush all 
objects rendered and thus cached, this will only work after the body has 
finished loading.  On the server-side of things you may use 
Page.Response.Clear(); or Page.Response.ClearContent(); which clears all 
content within the buffered stream.

hth,
Al


>From: "Debreceni, David" <david_debreceni@r...>
>Reply-To: "ASPX_Professional" <aspx_professional@p...>
>To: "ASPX_Professional" <aspx_professional@p...>
>Subject: [aspx_professional] Server.Transfer Issue
>Date: Wed, 14 Aug 2002 11:59:31 -0400
>
>I have a problem when I try to do a server.transfer on my page to a custom
>error page.  The issue is in a javascript menu system that we use.  The
>source of the error page is the actually the source of the page that
>generated the error, which to my understanding is the way it should be for
>server.transfer.  What I need to try and figure out is if there is a way to
>clear that content before the error page is rendered.  We get a scripting
>error when the error page is closed, I am guessing because the script is
>looking for items in the document that do not exist.  Any thoughts would be
>great.  BTW the only reason we want to try and avoid response.redirect is
>because of remote dialup users.  Thanks
>
>
>David Debreceni
>Senior VB/ASP Developer
>David_Debreceni@r... <mailto:David_Debreceni@r...>
>xxx-xxx-xxxx  x1086
>
>
>
>---
>
>ASP.NET 1.0 Namespace Reference with C#
>http://www.wrox.com/acon11.asp?ISBN=1861007442
>
>ASP.NET 1.0 Namespace Reference with VB.NET
>http://www.wrox.com/acon11.asp?ISBN=1861007450
>
>These books are a complete reference to the ASP.NET namespaces
>for developers who are already familiar with using ASP.NET.
>There is no trivial introductory material or useless .NET
>hype and the presentation of the namespaces, in an easy-to use
>alphabetical order ensures a user-friendly reference format.
>We provide in-depth coverage of all the major ASP.NET classes,
>giving you those real-world tips that the documentation doesn't
>offer, and demonstrating complex techniques with simple
>examples.
>
>---




_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


---

ASP.NET 1.0 Namespace Reference with C#
http://www.wrox.com/acon11.asp?ISBN=1861007442

ASP.NET 1.0 Namespace Reference with VB.NET
http://www.wrox.com/acon11.asp?ISBN=1861007450

These books are a complete reference to the ASP.NET namespaces 
for developers who are already familiar with using ASP.NET. 
There is no trivial introductory material or useless .NET 
hype and the presentation of the namespaces, in an easy-to use 
alphabetical order ensures a user-friendly reference format.
We provide in-depth coverage of all the major ASP.NET classes, 
giving you those real-world tips that the documentation doesn't 
offer, and demonstrating complex techniques with simple 
examples.  

---


  Return to Index