>Really?... What if the non-interest is that VFP's interop capabilities have been so well hidden and/or MS continues to malign COM+ when it suits yet promote it when it also suits???

What the heck are you talking about? .NET supports interop just fine, the problem is that lazy developers don't go out and find the information. If you're interested in Interop with .NET go buy a book and read up on it. There's a ton of material out there on the topic.

It's no rocket science either. It's not like making Windows API calls with Structures from Visual FoxPro. Now there's something that's hard to do.

Or go search the Web there are tons of articles out including two extensive ones from myself that talk about the basics and intermediate topics, and I'm working on another series of advanced topics. And you odon't just have to look at Fox related articles either.

The whiners are too lazy to do the work themselves!

I agree 100% with Rod that Interop is not a strategic choice. Nobody in their right mind would say: I'm going to build a new app today and I'm going to make sure it mixes both Fox and .NET together... There may be good reasons for using Interop in existing applications because they must talk to another application that runs .NET, but new application development is not one of them. Pick one or the other but not both as a strategic choice.

Further, when you do interop you'are going to find out that the developers that have to do it, will very quickly realize that doing the same thing in pure .NET is often much easier than dealing with the operational nightmare that COM Interop is.