information on Server.transfer object

Question

0.00/5 (No votes)

See more:

please can any body help me out in this regard

I have one doubt,I have created two web applications and hosted on local iis.In first application i have one web form in that one button control is present,in button click event i have written Server.Transfer("http://localhost/app2/Webform1.aspx");means i am trying to navigate second
webapplication's webpage that is webform1.aspx .which as virtual path as in serverobject .but it showing error provide virtual path .Is it possible to navigate to other app page which is present int same server

Posted 19-Jul-13 4:24am

chandubbbb

Add a Solution

Comments

ZurdoDev 19-Jul-13 10:41am

It is possible. Why don't you just do Response.Redirect? Also, what is the error?

chandubbbb 20-Jul-13 6:15am

ya we can do with response.redirect but compare to response.redirect ,server.transfer is faster
it uses onely one request and response cycle .and the error was stated like"provide virtual path"

ZurdoDev 20-Jul-13 17:26pm

1. If you provide the exact error that would help.
2. Yes, response.redirect has a roundtrip but it isn't slow enough for a user to notice, usually.

[no name] 19-Jul-13 11:15am

Server.Transfer("~/app2/Webform1.aspx");

You try this code

chandubbbb 20-Jul-13 6:19am

I have tried as above no use. Actully ~ symbol brings the control to root directory of the project but here we need to come out of the project and need to navigate other webapplications web page

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)