Single-Threaded Apartments vs Multi-Threaded Apartments [duplicate]

Question

Possible Duplicate:
Could you explain STA and MTA?

All ThreadPool threads are in the multithreaded apartment.

--As per the MSDN

What does that mean? I am really concerned with what the difference between the multi vs single threaded apartment model is. Or what does the apartment model mean? I have read the MSDN on it, and it doesn't really make sense to me. I think I may have an idea, but I was thinking someone on here could explain it in plain English.

Thanks, Anthony D

Update 1

Found this Could you explain STA and MTA?

Can anyone be more descriptive?

Update 2

I am also looking for an answer about how this applies to the thread pool, and what I need to watch out for because of this.

Answer 1

STA (single-threaded apartment) and MTA (multi-threaded apartment) are to do with COM. COM components can be designed to be accessed by a single thread, in which case it they are hosted in an STA, or they can be made internally thread safe, and hosted in an MTA. A process can have only one MTA, but many STAs. If you're only going to consume COM components all that you really need to know is that you have to match the apartment to the component or nasty things will happen.

Answer 2

In actuality, STAs and MTAs have an impact on .NET code. See Chris Brumme's blog entry for way more detail then you probably need:

https://devblogs.microsoft.com/cbrumme/apartments-and-pumping-in-the-clr/

It's really important to understand how STAs pump messages in .NET. It does have consequences.

Answer 3

If your COM object needs to believe that it is in a single-threaded environment, use STA. You are guaranteed that the creation and all calls will be made by the same thread. You can safely use Thread local storage and you don't need to use critical sections.

If your COM object can be accessed by many threads simultaneously, use MTA -- there will be no guards put in place.

Answer 4

As others have pointed out, it generally has little impact on .NET applications.

However, be aware that the Microsoft test host used for unit tests is actually implemented in an STA, which means that there are limitations on what you can do in unit test. For example you cannot do a WaitAll on a WaitHandle in a unit test is you're using Microsoft's test host.

Answer 5

You don't have to worry about it unless you're doing COM-interop, in which case there are marshalling issues. It has no ramifications for .net itself.