Let's get one thing straight. I am not focused on VFP and haven't been for some time.

I know the feeling: I left VFP for Java in 1997 and would have insisted that I no longer focused on VFP, except that I still checked out VFP forums and made an effort constantly to test/validate my decision. IOW I didn't burn any bridges, just as you obviously haven't. Which is cool. ;-)

I'm not actually interested in what eT is doing either.

Which is why you opened a thread about it. ;-)

My main temptation into making the cardinal sin of actually posting (as opposed to lurking) on this board was the claim that .NET as a platform was not mature.

How do you define mature? Can you teach an old dog new tricks? NET is all about new tricks. Compare with VFP whose data-handling and in-line SQL is largely unchanged for two decades. I have working FP data algorithms that were written before Windows existed and have never required a rewrite to remain contemporary. I have some of those same algorithms rewritten for L2SQL last year before MS effectively sidelined L2SQL. I'm not wanting to argue this point, especially since NET backward compatibility has improved substantially since 2.0, but in context it seems valid enough in a VFP forum.

From my perspective, I can personally gain much from Web2/AJAX technologies because this kind of development is plentifull and relevent in today's world.

Of course I agree and made similar comments regarding LAMP when Linq was released. So I'm curious: had eT decided to compile to LAMP rather than NET, would you still be disinterested?

I fell foul of being a "died in the wool" VFP developer and trying to find work with that skill-set on my CV. My reality is that quite some time ago, the Fox job market dried up here despite there being countless jobs for other MS and non-MS technologies.

You're saying there are lots of NOLOH jobs? Of course not. There are Web2/Ajax jobs. You plan to use a 3rd-party tool to improve your effectiveness in prevalent technologies. eT offers a 3rd-party tool to improve effectiveness in prevalent technologies. That's the angle that interests me. To be very clear: what eT promises is delivery of 100% NET IL or binary x86/x64. IOW NOT a VFP app. It's a NET app. Theoretically you could decompile eT's output to C#, compile back to IL and it should still work. In context, the compiler is a 100% NET tool- even if it does have the dreaded VFP taint.;-)

I couldn't really comment on what benefits eT will offer you but what I can say that I am building a system right now with NOLOH that works and that I can touch and feel. For my requirements, I can assure you that NOLOH delivers me far more benefits than eT could.

Then you should use NOLOH. I've reviewed the benefits of NOLOH and as I've already said, I hope that its beta continues successfully and that it meets its milestones. I have the same hopes for eT.