>>My first thought was yes. Why should there be a limit? The problems are that as soon as you impose a limit, you need to break it soon after. Perhaps we can live without WinForms, but WebForms and non-UI classes should be available.
>
>I think WebForms from VFP would be great. Perfect complement.

Why wouldn't you just do this sort of thing from the .NET IDE? For example, lets say you have your own classlibrary of controls. If you want to drag and drop - how would you do that in Fox?

Today, if there is a .NET class you need, you have COM/Interop - and you can do it today (and have been able to do it for quite some time). MS spending anytime or capital on this is absurd and leaves me a bit non-plussed in light of Steve Balmer's recent announcement that 1 Billion $ is going to be slashed from expenses. No doubt, there will be a lot of pencil sharpening going on as they "trim the fat"..

Think about it..... VFP never had true COM Debugging and it never had a decent interface to SQL Server - two things that could have been useful in Fox. All the time, we were told "it will cost too much" Or, what do you want to give up in exchange for those features. Also, we were told many times, the EM and QA apps are sufficient - and it would not be cost justifiable to "re-invent the wheel" in Fox.

Fast forward now to notion of accessing and interacting with .NET classes "natively" in Fox. How significant could it be? My guess, if anything happens, there will be class wrappers that take care of the process for you. Or, indeed, a utility that could, through a text merge process, generate the .NET classes. Anyway you cut it, it will be something that may save some work - but in the long run wont. To do anything else - would cost too much money.

If they did not do it for COM Debugging and/or SQL Server, why would it be done for .NET - especially when a very few Fox developers would ever take advantage of it.