|
-
Nov 25th, 2003, 08:45 AM
#1
Thread Starter
Frenzied Member
Server.transfer
Are there any known/common problems with using server.transfer("whatever.aspx")? It's always worked fine on my machine but after uploading to the live server today my web application hangs whenever i reach a point where server.transfer occurs.
Any ideas?
-
Nov 25th, 2003, 10:32 AM
#2
PowerPoster
I haven't really read up on the difference, but I always use
Response.Redirect
-
Nov 25th, 2003, 10:49 AM
#3
Thread Starter
Frenzied Member
I think i'm using server.transfer because it's needed because i'm using properties on one page that i want to be accesable on the following page.
eg.
VB Code:
Public ReadOnly Property CorrectPage() As Boolean
Get
Return ChoicesEntered()
End Get
End Property
The reason i'm doing this is because it's the tidiest way i've found of not letting a certain page load if the user hasn't taken the route through the site that i want them to.
Anyone know of any reason why this isn't working now it's not on my localhost?
-
Nov 25th, 2003, 01:18 PM
#4
Thread Starter
Frenzied Member
Bonkers absolutely crazy, after trying nearly a million things to sort this out, someone suggested renaming the page as they couldn't think of anything else, so i made a new page copied all the code(html and codebehind) from the original and it works now!!! what the hell is all that about?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|