ASP.NET 2.0 BasicsIf you are new to ASP or ASP.NET programming with version 2.0, this is the forum to begin asking questions. Please also see the Visual Web Developer 2005 forum.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the ASP.NET 2.0 Basics section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developersí questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
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).