Memory and session disposal, best practices

You can manage the Application SessionTimeout Event….

sessionstate is not a Wisej option. It’s Asp.net. The session timeout in wisej is an option in default.json – refer to extensive online documentation.

If you have a memory leak in your code use the memory profiler to find out which root in your code is holding references.

You don’t need to change anything related to the GC. It’s all handled automatically by .NET. Wisej doesn’t have anything to do with memory management and there is nothing for you to change other than avoiding memory leaks.

Memory leaks in .NET occur when you have a root (see .NET documentation about roots and garbage collection) that holds on a reference. It’s all standard .NET stuff – it’s not and cannot be changed by wisej or any other framework.