>>Yes. Sometimes the most tedious part of working with .NET was knowing how to do something in VFP, but not knowing even what it might be called in .NET, or where to look in the help.
>
>You bet... I´m losing a lot of time to figure out some basic stuff... but, well, it´s a whole new world for me (with no C-Like background).

That's nothin' compared to Beta 2 of .NET breaking all your Beta 1 code, or having to reformat your harddrive inbetween updates. *bg* Seriously, I know what you're saying. I think Cathi Gero said she read something like 2000 pages of documentation...and that was last fall. Kevin McNeish told the Seattle Fox User Group that he spent two months just diagramming the Framework. But all that work others have been doing for 2 years should help us get up and running a lot faster.

Another thought is this...one thing the Fox community has that seems to be somewhat lacking in others is the focus on supporting tools. Frameworks, whitepapers, and other sorts of tools (like Cristof's Struct, for example) that peers provide each other. No doubt that philosophy will continue.

>>One thing we want to do is make sure that where it makes sense to use the native code, that's made clear. For example, some functions are really better handled directly in C# or VB.NET.
>
>
>Yes... anyway, it´ll take a lot of time to be used with .NET and then, decided what aproach is better... but I´m on my way. :)

Definitely give us your thoughts as you go. This is a community based effort all the way.