Hello Andy (of MetaBuilders fame?), Communication from ASP.NET to windows services is not very good, AFAIK you can only do an ExecuteCommand with one parameter - a number between 1 and 128. If you need more communication than that from ASP.NET to your thread and want a thread to live during the entire lifetime, then you could try disabling recycling and idle-shutdown in your application pool settings. This allows you to create a thread that doesn't die off and remains during the entire lifetime of your asp.net app.
-Brian On Tue, February 28, 2006 11:32 am, Andy Smith said: > 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 > > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
