>>>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. :-)

Correct me if I'm wrong but isn't VB.NET getting freethreading? That's what's keeping us from making poolable objects...

> 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?

That is sort of funny. But if you think about it, there's no reason that IObjectControl couldn't be used for a homegrown pool manager. The three methods are intuitively names and are for pretty simple concepts that any pool manager would want to use.

> I suppose if I really cared I could try it and see what blows up.

You mean try implementing IObjectControl with VFP to see if you can get it to pool? Won't work- component Services checks the threading model before enabling the option in the Application properties sheet.