Assistance needed for COM+ - .Net Interop problem

We have a whole suite of Visual Basic 6 components that are used in a traditional ASP application and run in COM+. The COM+ components access frequently the IIS objectContext to retrieve session variables. In the ASP web application everything works well. We have now developed a number of .Net Web services that access the same set of vb6 components. Because the web services are .Net web services, each time a service is called, only an ASP.Net session is created. There is no ASP session or IIS ASP objectContext. As a result, the vb6 components included in the web service all fail as soon as they call the objectContext. We do not want to pass all variables which we need in any of the components as parameters from one method call to another. This should solve the problem, but would mean that we have to rewrite lots and lots of code. What we need is a replacement for the session and objectContext calls that we do in the vb6 component. Example: a web service method includes a paremeter 'customer code'. This 'customer code' is set as a session-specific parameter and the web service is consumed. When the vb6 component needs to access the customer code, the component reads the session-specific parameter and retrieves the correct customer code. If at the same time another web service call is started with another customer code as parameter, both web services and vb6 components must always use the correct customer code. If you think you can help us solving this problem, please respond to this mail. ## Deliverables Exclusive and complete copyrights to all work purchased. ## Platform Windows 2000 or 2003 ASP ASP.Net COM+ Visual Basic 6 C#