John Baird
Coatesville, Pennsylvania, United States
General information
Category:
Visual FoxPro and .NET
I swore I wouldn't get involved in another of these threads, but I can't pass up this comment. You can't judge another development platform based on whether or not it works with an outmoded development technology. VFP has its place (I still develop in it) and it is not .net interop. If you want .net, write .net, if you want vfp, write vfp.
>I don't have any doubt that Winforms will someday be there, if it isn't already - given the fact that MS is investing so much in it. I think the more important question is how well vfp will work with it, how developers can re-use their existing VFP investment with things like interop, and is there a place for developers who would still rather code in VFP (interop would again come into play here)...
>
>>Don't rush it <g> perhaps you won't have a second chance to impress die-hard vfp'ers
>>
>>
>>>Glad to see your google works.
>>>
>>>Now I would like to see you find 3 different .NET developers that agree on an approach to anything.
>>>
>>>You take Rick's word as gospel. There are many that would disagree with his assesment.
>>>
>>>BTW, the example app is almost done. I should be posting it later tonight or early am. I am at a conference now, so between and during sessions I worked most of it up.
>>>
>>>Rodman
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