how to call aspx page from class

Question

1.00/5 (2 votes)

See more:

ASP.NET

i dont know how to call aspx page from .cs class it is not code behind class it is other class

Posted 11-Jun-11 19:18pm

mohit.a44

Add a Solution

Comments

thatraja 12-Jun-11 2:36am

for what? why? give us some details.

Sandeep Mewara 12-Jun-11 4:00am

Not clear.

2 solutions

Add a Solution

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)

Srinivas Kumar Pasumarthi · Answer 1 · 2011-06-11T19:24:00

Solution 1

using Response.Redirect("Page Name ");

using this we can navigate from one page to another page

Posted 11-Jun-11 19:24pm

Srinivas Kumar Pasumarthi

Comments

mohit.a44 12-Jun-11 1:27am

response obj not in class

CDP1802 · Answer 2 · 2011-06-11T20:10:00

Without knowing more about what you are trying to do, this sounds like you have a problem in the application's class design.

ASP.Net pages are objects like all others. So far we have no problems. Other objects can call the page's methods or use its properties. All they need for that is a reference to the page object.

Unlike other objects, a page only exists for a short time. An instance of the page is created when the server receives a request. Then the page goes through a series of actions (initialization, PageLoad, events from controls, PreRender...) with the goal of generating a response which is then sent to the browser from where the page was requested. After that response has been sent, the page object is destroyed.

Your other object would need a reference to the page object to call its methods. There is no mechanism that tells a class wether or not an instance of a page exists at the moment.

And this is why I fear you may have a flaw in your design. The more logical approach would be that the page creates or obtains references to other objects and then calls their methods, not the other way around.

In such cases, when it becomes hard to make two ends in a program fit together, redesigning usually is the better way to go. This would eliminate the problem instead of working around it to cover up the symptoms.