What is the best practice of clearing all unused objects when done using them and clearing all Session variables when user clicks log-out?
I think the following problem has something to do with this:
I'm having a frequent issue for an application I developed for corporate customers. The user sometimes experience logging in problem, on the authentication page, which would fail to issue a database query through which the user get authenticated by a password. However after I restart the IIS (without doing anything else to the code), the log-in starts to function again.
Any advice would be appreciated.
Yubo

To clear the session variables, you can use the Session.Abandon method at log out.

- - - - - - - - - - - - - - - - - - - - - - -
In God we trust, everything else we test.

how about other objects, like running database threads and business objects, which are not perfetly handled by CLR gabbage collections.

I think you are better off letting the garbage collector do its thing, however you may find this useful.

http://msdn.microsoft.com/library/de...Collection.asp

- - - - - - - - - - - - - - - - - - - - - - -
In God we trust, everything else we test.

One thing I can recommend is to make sure you close your database connections. Otherwise, like the colonel says, let the CLR garbageman do his thing.