Assumming you've tried the page attribute I mentioned in my previous post, there's not much to suggest, but to marshal all calls to the component's creator thread. One thing I can't know is whether the component is stateless or statelfull (and whether it's cheap or expensive to create), and whether you can simply create it every time and on any thread and use it there.
Cheers, Stoyan On 2/28/06, Andy Smith <[EMAIL PROTECTED]> wrote: > Thanks, that's a great point, I believe I do have the thread affinity > issue with this COM component. You remind me that I had to make a config > file modification in a test project because of this (VS2005 Team System). > > *sigh* Thought I could get out of this on the cheap, but I guess I'm stuck > with having to do a full-blown implementation with a separate thread just > for the COM object. > > Here's a followup question, then: what's the *easiest* way to do this? Can > I do this all within the same ASP.NET application? Can I just grab a > thread from the thread pool, maybe started from the Application_Startup > event, and just have it live during the entire lifetime of the ASP.NET > application? Or would I be best off in a separate process, i.e. a windows > service? > > Thanks again. > > Andy =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
