classic asp w/ asp.net

[jjmendo]

I need to update an application that was written in classic asp. Due to time concerns I can't update the entire application right now, but users need some functionality change in a couple of the pages. Would I be able to create these pages in ASP.net. Would the application allow both asp.net and classic asp pages. Thank you.

 

[Veep]

Yes. Both will run fine in the same virtual.

 

[jjmendo]

Thank you for the quick reply. Would there be issues when transferring information between the old and new pages. I haven't developed in classic asp, does it support querystrings, storing server session info. Two scenerios,

1. classic asp transferring data to asp.net pages
2. asp.net transferring data to classic asp pages

Thank you.

 

[Veep]

You shouldn't have any problem using querystrings or session objects. As you probably know ASP.NET pages are designed to post to themselves. To fake a post to another page you would do a Server.Transfer() but I can't say if it's going to work going from ASP.NET to classic .ASP. I've never tried it but I don't think that Posting form data from a classic .asp page to a ASP.NET page is going to fly either. As long as you keep in simple (querystrings,session state) you should be ok. If you try some of the stuff like posting form data and you're able to make it work, please post back to this thread with your results. I'd like to know. Thanks.

 

[ca8msm]

Also you can share session information between the asp and .net application. Check out the following link for some more info:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/converttoaspnet.asp

----------------------------------------------------------------------

Need help finding an answer?

Try the search facilty (

http://www.tek-tips.com/search.cfm)

or read FAQ222-2244 on how to get better results.

 

[link9]

Posting form data will work between ASP & ASP.NET. Posting data is really part of the http world, and is completely separate from ASP or ASP.NET.

As Veep pointed out, though, ASP.NET pages want very badly to post to themselves, so you need to work up something custom to make them post to different page. MetaBuilders has a nice control for just that (

http://www.metabuilders.com/Tools/CustomForm.aspx).

ASP & ASP.NET will (technically speaking) play nicely together. However, if you continue to build ASP.NET on top of an existing clASP implementation, you will wind up with one big kludge of an application.

The only reason to EVER do this would be time constraints, and by its very nature, that puts your architecture decisions at risk of being rushed. Plus, you're building on top of an architecture that didn't even allow you to make good architecture decisions (clASP). All this is a recipe for a less-than-spectacular application.

Just a word of warning. Personally, I would never do it again. If it was a requirement of the job, then I would pass on the job.

-paul

The answer to getting answered -- faq855-2992