>>>VFP won't target the CLR. Other than that, VFP can do whatever you want with .NET. Queued components? It's in there. Compensating Resource Managers? Yeah, we got that, too. Loosely-coupled events, tightly-coupled events, it's all in there.
>>
>>Object pooling? Nope. :-)
>
>Ah, but we can take solace in the fact that VB can't, either. :-) Oddly enough, though, MSDN shows the syntax for implementing the IObjectControl interface in VB. Huh? What good is that going to do if VB only does apartment model threading, and thus can't be pooled? I suppose if I really cared I could try it and see what blows up.

Curious, since if you dig through the .NET docs, the thread model for CLR components seems tied to one of the .NET resource classes, implying at least that the threading model resource is subclassable directly through a CLR language construct. Maybe I'm mis-reading the docs, but it reads like there's a threading resource...