Hi Kevin !
Thanks for your answer.
As regards as intellisence: "VB has much richer fidelity between intellisence and the compiler (VB uses background compiler, C# user parser for intellisence)" Drew Fletcher, Product Unit Manager (MSFT)
To be honest - I still rather evaluate then realy use VS.NET . So I can't say how much important is this difference in real coding. I was rather looking for the anwser.

>Jozef,
>
>>First reason: case sensivity - it looks that it can drive mad a VFP developer.
>
>This can drive you crazy at first! However, after a little while, you don't think much about it, and use it to your advantage!
>
>>Second reason: intellisence - it seems that in VB.NET it is made more comfortable than in C#.
>
>Can you give me a specific example?
>
>>Third reason (main reason): If in a future I will develop/maintain several projects some in VFP some in NET, it seems that it will be easier constantly switching my mind between VFP and VB.NET than between VFP and C# -just because many VFP language are VB like not C# like.
>
>Maybe, maybe not. There are a number of VB developers who decided to use C# because it's *less* confusing to them, since VB and VB .NET are so close in syntax. Personally, I switch back and forth between C# and VFP easily!
>
>Regards,