Hi Kamal,

Ahhhh Ok! So to me, it's no big deal. It's much like Ken is saying that VB.Net is easier to learn by VFPers.

>Hi Jess,
>
>C# supports importing namespaces only into your source files. What does this mean?
>
>As an example, the VFPToolkitNET.DLL library is defined in the namespace "VFPTooolkit". When using this in a C# project you can only specify "using VFPToolkit;". This means that if you need to access any classes in the toolkit you need to explicitely specify the full path:
>
>

>// C# source
>using VFPToolkit;
>
>strings.FileToStr(@"c:\myfile.txt");
>//or
>VFPToolkit.strings.FileToStr(@"c:\myfile.txt");
>

>
>On the other hand VB.NET supports importing namespace.class in your project so we can say:
>

>' VB.NET source
>Imports VFPToolkit.strings
>
>FileToStr("c:\myfile.txt")
>

>
>The difference in the above two is obvious that in VB .NET you are writing the exact code that you would in VFP. If fact allowing you to cut and paste.
>
>Kamal
>
>>Hi Kamal!
>>
>>>The VFP Toolkit for .NET is equally compatible in both C# as well as VB .NET. The source code is also available in both C# and VB .NET.
>>
>>Then why is it that there is a statement saying VFPToolkit will work more seamless in VB.Net than in any .Net language?