Question

I have tried to make a webservice interface to a state-holding COM component.

The webservice basically contains operations Start, Shutdown and GetCurrentState.

Start creates a COM component, Stop releases.
And GetCurrentState retrieves information from the COM component.

It seemed an easy thing, but after a day it still refuses to work.

I have tried storing the COM-reference as a member variable in the C# object. The object is constantly re-created.
Then I tried to store the COM-reference in the Session object. But still, something is still wrong.

Anyone know how one should store COM reference which should stay alive inside webservices?

/L

Answer 1

Assuming you are using ASMX here, and not WCF where you could control the life time little bit differently, each time a request comes in the class that services the request is recreated. This is the standard behaviour for ASMX.

What you need to do is store the COM object either inside the Cache[] or Application[] collections. It may still get destroyed when the worker pool is recycled. Some code like this is what you need:

public FooClass GetFooClassInstance()
{
    FooClass instance = (FooClass)this.Context.Application["FooClassInstance"];

    if (instance == null)
    {
        instance = new FooClass(); // Creates the RCW.
        this.Context.Application["FooClassInstance"] = instance;
    }

    return instance;
}

The FooClass is the runtime callable wrapper for your COM object. The Application object contents is retained between requests. One thing you do need to watch out for is the threading model that the COM component is using as some can cause performance problems because they marshal calls onto a single thread.