P
pmccombs
I have a situation where I am migrating some ASP pages to ASP.NET. A
particular page that I have migrated #includes another ASP page that is
not going to be migrated. This is unforunate because it causes the two
pages to be "mixed" together, resulting in a part of the page that
needs to be processed with the ASP filter, and another part that needs
to be processed by ASP.NET.
Is there a way that I can initiate a new server request during the
ASP.NET processing, obtain the HTML result of the new request (using
the ASP page), and then render that result into the original ASP.NET
request?
I've heard of 3rd party "bridge" software that can do this, but that is
really not an option with my project. I'm hoping there is a fairly
simple way to do it, otherwise I will have to convert all of the ASP to
ASP.NET.
particular page that I have migrated #includes another ASP page that is
not going to be migrated. This is unforunate because it causes the two
pages to be "mixed" together, resulting in a part of the page that
needs to be processed with the ASP filter, and another part that needs
to be processed by ASP.NET.
Is there a way that I can initiate a new server request during the
ASP.NET processing, obtain the HTML result of the new request (using
the ASP page), and then render that result into the original ASP.NET
request?
I've heard of 3rd party "bridge" software that can do this, but that is
really not an option with my project. I'm hoping there is a fairly
simple way to do it, otherwise I will have to convert all of the ASP to
ASP.NET.