I think that limitation will knock down most vfp users requirements.

I also think that one of the problems with us targeting specific .net areas is that we are all projet based and it would be unlikely many of us are at the design stage where we can consider integrating some .net functionality. I recently wrote a fll to allow me to ping a network ip address, this would have taken 2 minutes in c# but instead was a pain in vfp (thus the fll), had I some way of interfacing with .net that had made this easier I would have jumped at it. But that was then and now I dont intend to re-engineer the system from the fll.

I am also concious of where we will stand with the new version of windows when we will in fact be making calls to .net wrapper instead of .net directly.

I understand that any release can be and will be analysed to death as some form of statement/policy move on behalf of Microsoft. I also accept that anything that goes out of the door requires resources that could be spent (and I accept possibly better) on some other project. However, I think I have an aversion to withholding anything that may be of some use to someone somewhere. Isn't this a similar position to that of the WTL for many years?

How about making it open source?