Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
DOT HISTORY will repeat itself
Message
 
To
21/10/2004 11:03:12
John Baird
Coatesville, Pennsylvania, United States
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Miscellaneous
Thread ID:
00950538
Message ID:
00953331
Views:
23
Well, much of the value of VFP is in the actual code. You seem to be one of these developers salivating at the thought of all the VFP code you'll be able to convert to .NET. I guess VFP to .NET interop sort of puts a kink in that plan...
>Its okay to use vfp data as a back end. That's okay. Where I draw the line, is using things VFP Toolkit in .net so you can continue to use VFP syntax, or trying to build components in .net to call from VFP. Its a folly to try to mix the two technologies. Pick one or the other. Hybrids of any type are usually a bad idea.
>
>
>>Needless to say, I disagree. Furthermore, to take your logic, why discuss using .NET here at all - if we're discussing developing .NET, why shouldn't that just be in the .NET forum? I would argue that most people in the VFP forum are interested in using both technologies together meaning "the best of both worlds", not the continued arguments for why they should switch to.NET. Even Rod's example is at least using a VFP DBC...
>>
>>>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
Map
View

Click here to load this message in the networking platform