Hi Kamal,
Aside from shorter learning curve benefit of VFPer moving to VB.Net what else you have in mind are the advantages other than using C#?
>Hi Jozef,
>
>
>Thanks Kamal for this info and for your work with VFPToolkit also.>
>You are welcome.
>
>
>I wonder if it wouldn't be better if VFP team CLEARLY said: "Hey people - direction is VB.NET you can work with VFP and C# but if you will use VFP and VB.NET your road will be more pleasant and we will support you in that direction more that in another">
>As your question is geared towards the VFP Team, I am not the right person to answer this. I can provide you my viewpoint on this and I think that no one is asking VFP developers to move to VB .NET or C#. The question is "For those VFP developers who want to use both VFP and the .NET Framework, which language should they pick?"
>
>I am merely giving a recommendation for VB .NET because of the two reasons I mentioned earlier and it also allows you to cut and paste existing VFP code straight into your ASP .NET apps or WinForms.
>
>Kamal
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."