>>All that aside, what can you do in VFP that you cannot do in .NET today?
>
>
Oh, man, you know as well as I do ... why ask the question? Native data, inheritance advantages, macro substitution, et al.
>
Sure, VFP has native data - but tht is not an advantage of VFP - that is just a difference. The fact is, whatever you can do with VFP+DBF's - the same can be done in .NET+SQL Server.
Inheritance??? You would have to clairfy this one. I have found zero issues with how .NET implements inheritance. If anything, .NET is better because if I ever want to change the parent class, I can do it with a simple code change.
>
Allow me to be crystal clear. I work on the Fox Team. My customers are the VFP community. I was a significant member of that community before I joined MS and that's where my loyalties lie. I will always state things the way I think benefits the community and my employer be damned.
>
So it is your opinion that Ken is being disloyal because of the work he has done with/for the .NET customer base?
Interesting info John.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only