I work on the asp.net website. We should use com interop to interact with legacy activex vb6 components. Components in many cases rely on receiving a context object (which is itself an active vb6 component) as a parameter. The context object is quite expensive to build.
Therefore, one idea is that the context object is built once and stored in the asp.net session. However, if this object is just a .net wrapper around the activex component, is it appropriate or advisable to keep such an object in the session?
In addition, the context object contains user-specific information, so you can use HttpRuntime.net cache storage, but this will require a specific user key.
I understand the other limitations and all you need to know with an asp.net session is the aspnet-session question .
Ask the question a little differently: do they have any problems or problems saving the .net object, which is just a wrapper around the com object?
source
share