General information
Category:
Visual FoxPro and .NET
I totally agree, Bob. C# was fairly painless. It's .Net that's the trouble. Though as I start to get it more and more, I'm starting to feel more and more like it's worth it.
I went with C# because I think VB.Net won't entirely escape the baggage associated with the fact that it is still a BASIC derivative, albeit mostly in name.
>Hi Kev,
>
>I agree with Cetin, the keywords in C# have a lot in common with VFP. My transition was to C# was fairly painless, it was the .NET framework that had the steep learning curve. It was well worth the effort.
>
>Regards
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only