Another good reason to look at .NET possibly more so than other languages is that you can at least interop with it from FoxPro. You can create a library in .NET and then call that from FoxPro either via COM Interop or via wwDotnetBridge to give you a big chunk of functionality that would otherwise not be available in FoxPro.

And for your Visual FreePro - you can also host .NET directly in your own application - which is pretty much what I do with wwDotnetBridge, so you can extend it that way as well.

+++ Rick ---

>I've looked at C# and .NET over the years, and have tried various things and had a general idea of how it worked, etc.
>
>I've had an occasion recently to learn more about it and I have to say I'm very impressed with how well integrated it is.
>
>For my Visual FreePro, Jr. database engine, I've had to create an external DllImport and use some marshaled unmanaged pointers for obtaining information back from the remote VJr DLL. It's been very straight-forward to integrate and is working well.
>
>

[DllImport("vjrdbf.dll")]
>public static extern UInt32 dbf_get_field_type_extended(Int32 handle, UInt32 fieldNumber, [MarshalAs(UnmanagedType.LPStr)] ref string dest, UInt32 destLength);
>

>
>It's really been quite nice. If any of you have been putting off learning C#, I would suggest you give it a try. It's very robust, and if you have any C/C++ knowledge, it's very straight-forward.