John,

>>I do know that Jess Banaga has a project rewritten in .NET but did not introduce it yet because of some performance problem.
>>
>>We won! We won! Thread #1043176 Message #1043176
>>
>>In the same thread, Neil mc Donald confirmed having the same problems, but I don't know the real story behind that. I know John Ryan has some experience in this field, but I'm not sure if he has a situation that is a honest comparison. You'll have to ask the named persons to get a full detailed description. Also Cetin, seems to have quite some experience in both, but You'll have to ask him if he applies to answering your question.


What is your problem? In this message I merely did answere tracy's question.

>Uh huh, and three unrelated developers have a problem with .net and that makes your case? They are VFP programmers; I wouldn't expect any different.

Eh, no, they are both VFP and .NET programmers, just like the ones who did do succesfull conversions. Jess was not taking my side of the stance when he started doing .NET, but more JVPs.

>During our migration effort, we hired experts in .net to come in and help set up our framework, our data procedures, our tools, etc. We then have been trained, and are now producing quality code in .net. We don't notice any difference in the speed of our apps except we have to do more processing on the server.

>You really need to learn what it is you are talking about before you present an argument.

Eh, so I can not listen to people who do have problems, but I should listen to you (with your history) and be a reliable source. Further Tracy did talk about DATA INTENSIVE applications, meaning there is a lot of data processing neccesary, not about applications that just get their data in a form they like from the SQL server and does not have much of a requirement of post processing data. Further you seem to totally ignore the conclusions from MS itself. And I suppose the LINQ won't solve anything in .NET because there are no data integration problems right? I think you better learn what is going on the the .NET community and draw your conclusions. LINQ is great and solves data integration problems. A greate source from this are the bloggs from YAG and the articles of the PDC and the threads here about LINQ. See why it is such a great solution and what it does solve for you. Then it becomes more obvious what currently is missing in .NET what VFP already has for 20 years. Read my friend, read...


Walter,