I have developed part of application in asp, now I am going to develop remaining part of the application in asp dot net. My question is whether it is possible to do so.

Suresh

Yes it is possible, however the 2 technologies don't share the same Session state so, any Session values created in asp will be inaccessible using the Session() object in .NET.

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from planoie's profile^^
^^Modified text taken from gbianchi profile^^
================================================== =========
Technical Editor for: Professional Search Engine Optimization with ASP.NET
http://www.wiley.com/WileyCDA/WileyT...470131470.html

Ok, Whether I will face any other problem other then Session for other scenarios

What are "other" scenarios?

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from planoie's profile^^
^^Modified text taken from gbianchi profile^^
================================================== =========
Technical Editor for: Professional Search Engine Optimization with ASP.NET
http://www.wiley.com/WileyCDA/WileyT...470131470.html

Other Scenarios like, Database connection, COM ,Cookies,application variable ,Passing Values between asp and asp.net pages,global.asa ,global.asax pages ,etc

Database connections are just connections. You can connect to the same database from any application that supports it without problems.

ASP and ASP.net can both use COM components without problems apart from the usual DLL hell and possible .NET interoperability difficulties.

You may experience problems with cookies because of the way application roots are written in cookies. A ASP.NET app will always have a virtual directory application (whether it's the server root or an actual virtual). ASP doesn't always follow the same pattern.

asa is for classic ASP. asax is .NET. The two don't mix.

Passing values between application contexts requires writing the values to a persistent medium (i.e. database, file, etc) or passing over the query string. As mentioned you can't share values using the *native* session technologies. That is not to say that a custom built session management system can't. However, you still need a way to carry a session identifier between the applications (usually querystring).

-Peter