Looking to settle an argument here.
All the stuff I\'ve read on using a COM object created in VB from an ASP.NET page is surrounding with
WARNING - MAKE
If you can modify the source of the COM object, you may be able to determine if its behaving as an STA through a simple experiment assuming you have a test environment.
Call sleep for some significant amount of time in the component, say 30 seconds and deploy the component.
Fire up a couple of browsers and hit the page requiring the component from two browsers at about the same time.
Assuming the page has no other significant non-deterministic delays, you should be able to tell if this is a MTA or STA. If both pages return at the same time ( after about 30 seconds ), the component is running as an MTA. If one returns in 30 and the other in 60, its running as an STA.
I would think that there is a way to inspect the registry or the dll itself as well, but it has been a little while since I was working in a mixed COM / ASP.NET world.
Good luck!