There’s nothing more amateur than displaying a big, yellow unhandled exception page for a .NET application. Professionally done ASP.NET websites need adequate error handling and recording. It’s not enough to catch exceptions and display a friendly error page — you need to record any unhandled errors so that they can be fixed.

The Session object is extensively used for many projects, but it is often misused to the point of becoming unwieldy if it isn’t appropriately managed.
The ‘Traditional’ Management
The traditional method of referencing a session key is to use a string literal:
Session("SessionID") = 12345
Session("SessID") = 12345
Session("SID") = 12345