Passing parameters between applications

[Archana]

Hi,

I want to forward a request as it is from an aspx page(could be a web
service too) in one application to another aspx page in a different
application. The intial request will be having parameters(not fixed
number) which I need to use in the second aspx page. I used
Server.Transfer but it gives me an error message -
Could not load type 'SubHandler.SubReqHandler'
which is the aspx page in the second application.

I am new to ASP.NET, could anyone tell me if it is possible to do
this?
If it is possible could you let me know what I am doing wrong or how I
should be doing it.

Any help would be appreciated. Thanks,

-Archana

[Natty Gur]

Hi,

As Far As I know you can’t use Server.Transfer to redirect user outside
your application boundaries. You should use Response.Redirect to
redirect to other applications. You can add query string to the redirect
URL. Don’t forget that there is a limit of 100K to the querystring. if
you want to move big chunk of data you better store it in DB and just
pass identifier to the calling application that will use the given
identifier to retrieve data from DB.

HTH

Natty Gur[MVP]
Phone Numbers:
Office: [phone]
Fax: [phone]
Mobile: [phone]
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Archana]

Thanks for the reply.

May be if I give my actual problem you can suggest me a solution.

I understand that it has to be under the same namespace if I have to
use Server.Transfer. I cannot use Response.Redirect as the parameters
are not fixed. The problem is I dont want to compile the whole
application each time I add a new aspx page. There could be hundreds
of pages eventually for my application to which the intial page has to
redirect. Is there a way around the compiling process so that I can do
it somewhat like a module and build that and add it to the
application. Hope I am clear enough. I use Visual Studio for
developing.Thanks,

-Archana

[Natty Gur]

Hi,

I understand that it has to be under the same namespace if >I have to
use Server.Transfer You mean same Application (application can contain several namespaces)
I cannot use Response.Redirect as the parameters
are not fixed But you can save the parameters in DB with identifier (GUID) send just
the identifier using redirect and query string and use the identifier on
the calling page to get parameters form DB
The problem is I dont want to compile the whole
application each time I add a new aspx page.

I dont get it, can you be more clear ?

Natty Gur[MVP]
Phone Numbers:
Office: [phone]
Fax: [phone]
Mobile: [phone]
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Natty Gur]

Hi,

I understand that it has to be under the same namespace if >I have to
use Server.Transfer You mean same Application (application can contain several namespaces)
I cannot use Response.Redirect as the parameters
are not fixed But you can save the parameters in DB with identifier (GUID) send just
the identifier using redirect and query string and use the identifier on
the calling page to get parameters form DB
The problem is I dont want to compile the whole
application each time I add a new aspx page.

I dont get it, can you be more clear ?

Natty Gur[MVP]
Phone Numbers:
Office: [phone]
Fax: [phone]
Mobile: [phone]
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Archana]

Yes, you are correct, thats what I meant, the aspx page has to be
under the same application.
I cannot use DB to store parameters.

What I meant by "I dont want to compile the whole application each
time I add a new aspx page" is -
If you are familiar with Java, the application is like a master
servlet and child servlets structure. In Java we can just compile the
child servlet individually and all that is required for it to work is
the class file to be in the correct location. So I wanted to know if
there is something equivalent to this structure in .NET and I need the
request to be forwarded as it is from the first page. Hope I'm clear
enough this time. Thanks,

-Archana

[Archana]

Yes, you are correct, thats what I meant, the aspx page has to be
under the same application.
I cannot use DB to store parameters.

What I meant by "I dont want to compile the whole application each
time I add a new aspx page" is -
If you are familiar with Java, the application is like a master
servlet and child servlets structure. In Java we can just compile the
child servlet individually and all that is required for it to work is
the class file to be in the correct location. So I wanted to know if
there is something equivalent to this structure in .NET and I need the
request to be forwarded as it is from the first page. Hope I'm clear
enough this time. Thanks,

-Archana