STAThread requirement for windows forms

Question

AFAIK, all Windows Forms application should set the [STAThread] directive above their Main() method.

However, there's an exception. We are writing applications for Windows Mobile devices, using the Compact Framework. Compact framework doesn't even support the [STAThread] directive, it only has the [MTAThread]. Still, I never encountered any problems there.

Now, to take it 1 step furhter, you can also run Compact Framework applications on a full blown windows system. I think that in that case the full blown .NET framework will be used.

At that point, we are running code with an MTA apartment state, which uses windows forms on a full blown windows system. This brings me to the question, if a compact framework application runs on a full blown windows operating system, why doesn't it complain about the lacking [STAThread] directive ?

Answer 1

As per This Answer I'd say it's not actually Windows Forms running on the normal machine but a subset. It could of course also be that some sort of proxying is going on and the framework is taking care of bootstrapping an STA thread and marshalling back and forth for you.

A comment on This Question specifically:

Simple CF apps will run without modification on desktop, this is well known. But apps that use CF-only APIs (ie aygshell related), will not run. The STAThread compile option can only be used during compile (AFAIK). If a DLL was compiled with that option I can imagine that it wil not run on desktop. For the web browser component, you need to not load this hardcoded but from within code and then load either the full framework one or the CF one. CF Forms are hardcoded to MTA. If a COM is loaded that requires STA, it will give exception.

By Josef, seems to indicate that the compact framework forms will happily trundle along under MTA, but freak out as soon as you use a COM-based component from winforms that does require STA.