Just to add on to Eric's email. There is a great book from
Hentzenwerke called: ".Net for VFP developers". This book is a great
introduction book for .NET and is written by a VFP guru. The author seems to
favor C# and says that C# is probably the best choice for VFP developers, but he
compares C# and VB.NET objectively.
?
Also there is a toolkit, Visual Fox Pro toolkit for .NET,
?available for download from
The toolkit includes a lot of the good ol' foxpro functions
and commands and is a great starting point if you want to get into
.NET.
?
Einar
?
Speaking of .NET, I know that PJ at one time in his consulting days
was learning C#.? Anybody else??? It's my understanding that C#
would feel more natural to us VFP programmers than Java even.
The mono
project on Linux, which allows C#, vb.Net, asp.net, ado.net, etc. to run on
Linux looks *very* interesting ().? Ironically if
Microsoft had ported VFP over to the .NET side, getting it on Linux would have
been much easier thanks to the mono project.? We could have just run our
VFP psuedo-code on the mono Common Language Interface (Interpreter?) on Linux
and been off and running!? Of course we'd probably have to use ODBC to get
at VFP data.
It'd be very ironic if Novell, with this mono project,
knocks Microsoft out of languages.? Personally I think Novell should spin
their Java development and app server (fka Silverstream) and Mono development
into a separate company, and then maybe even merge that company with Borland who
really has language expertise.? Ideally then Borland, who had dBase
experience way back, could create a VFP clone or host an open-source VFP
clone.? Yeah, that'd be awesome.
There's still talk about IBM buying
Novell though, which I'd hate to see happen.? IBM's overloaded with too
much stuff as it is.
Eric
Stein Goering wrote:
toggle quoted message
Show quoted text
The .NET juggernaut
keeps on rolling, and will probably ultimately lead to the fox¡¯s demise,
though not as quickly as some have predicted.??
