Mixing classic ASP and ASP.NET in one webapplication

Report · Nov 28, 2006

Hi,

We have developed a commercial webapplication in classic ASP, but we would
like to move on to ASP.NET.

At this point, it is not possible to sit down and rewrite the whole existing
application, because it would simply take too much time which we don't have
right now.
But we would like to start developing new functionalities in ASP.NET and
somehow integrate them with the classic ASP application.
And then we can gradually rewrite the older functionalities in ASP.NET as
well.

Has anyone tried this before (integrating classic ASP with ASP.NET)?
And if so, do you have any tips for us on how to go about this?

Regards, Marja

Report · Nov 28, 2006

It's easy as pie. :)

The only thing you'll need to do is make sure that any ASP session variables
are set for ASP .NET and vice versa. This is usually only an issue at
login. What I did was have my classic ASP login page redirect to a .NET
page after it created the ASP session variables. The .NET page just needs
to duplicate those, then redirect to wherever the user would have gone
anyway.

Other than that, Server.Transfer won't cooperate for obvious reasons, but
Response.Redirect from ASP to ASPX is no problem at all. The two can
otherwise co-exist seamlessly.

"Marja de Vroed" <marja@clubwebware.nl.no.spam> wrote in message
news:ekhirh$h8a$1@forums.macromedia.com...
> Hi,
>
> We have developed a commercial webapplication in classic ASP, but we would
> like to move on to ASP.NET.
>
> At this point, it is not possible to sit down and rewrite the whole
> existing application, because it would simply take too much time which we
> don't have right now.
> But we would like to start developing new functionalities in ASP.NET and
> somehow integrate them with the classic ASP application.
> And then we can gradually rewrite the older functionalities in ASP.NET as
> well.
>
> Has anyone tried this before (integrating classic ASP with ASP.NET)?
> And if so, do you have any tips for us on how to go about this?
>
> Regards, Marja
>

Report · Nov 28, 2006

Ah yes, I know they can co-exist on separate pages in the same website.
But in some cases I would need them to function together on the same page,
which I know is not possible natively.

But to do that anyway, I'm thinking about using Ajax techniques to "import"
result code from new ASP.NET functionalities in some classic ASP pages.
Have you tried that?

"Lionstone" <HIDElionstone@HIDEhushmail.com> wrote in message
news:ekhoe7$nsu$1@forums.macromedia.com...
> It's easy as pie. :)
>
> The only thing you'll need to do is make sure that any ASP session
> variables are set for ASP .NET and vice versa. This is usually only an
> issue at login. What I did was have my classic ASP login page redirect to
> a .NET page after it created the ASP session variables. The .NET page
> just needs to duplicate those, then redirect to wherever the user would
> have gone anyway.
>
> Other than that, Server.Transfer won't cooperate for obvious reasons, but
> Response.Redirect from ASP to ASPX is no problem at all. The two can
> otherwise co-exist seamlessly.
>
>
> "Marja de Vroed" <marja@clubwebware.nl.no.spam> wrote in message
> news:ekhirh$h8a$1@forums.macromedia.com...
>> Hi,
>>
>> We have developed a commercial webapplication in classic ASP, but we
>> would like to move on to ASP.NET.
>>
>> At this point, it is not possible to sit down and rewrite the whole
>> existing application, because it would simply take too much time which we
>> don't have right now.
>> But we would like to start developing new functionalities in ASP.NET and
>> somehow integrate them with the classic ASP application.
>> And then we can gradually rewrite the older functionalities in ASP.NET as
>> well.
>>
>> Has anyone tried this before (integrating classic ASP with ASP.NET)?
>> And if so, do you have any tips for us on how to go about this?
>>
>> Regards, Marja
>>
>
>

Report · Nov 28, 2006

> But to do that anyway, I'm thinking about using Ajax techniques to
> "import" result code from new ASP.NET functionalities in some classic ASP
> pages.
> Have you tried that?

Oh, no problems there. I use Remote Scripting all the time. Because I have
to support old browsers, I fall back on the old hidden IFRAME technique
rather than using the browser's XMLHTTPRequest object (only recently have
browsers other than IE been equipped with such an object; IE has had it
since '98). Even so, I can't see any problems using either method since the
client-side scripts won't change based on the server-side technology.

Report · Nov 29, 2006

> Oh, no problems there. I use Remote Scripting all the time. Because I
> have to support old browsers, I fall back on the old hidden IFRAME
> technique rather than using the browser's XMLHTTPRequest object (only
> recently have browsers other than IE been equipped with such an object; IE
> has had it since '98). Even so, I can't see any problems using either
> method since the client-side scripts won't change based on the server-side
> technology.

Thanks, I will start experimenting then. :)

regards, Marja