>Hello.
>
>I´ve been looking at VFP Compiler for NET. Realistically, you may expect to be at 95% VFP compatibily in a couple years. This way, you may end rewriting 10% of your code to update your current VFP projects to .NET instead of the .NET learning curve plus rewriting of projects. Still worthy the wait, specially if you have a big codebase with lots of customers. Also you may expect to extend your codebase in those 2 years to come without the fear of having to rewrite the entire thing in another language.
>
>
>I've been thinking in ways to finance the entire thing, maybe evangelizing it more, looking for seed capital, angel investors, and so on. The more money is in etecnologia, the faster and better the results. Any coment?
>
>Regards

What do they (Etec) really need? They have to communicate themselves what they want: money, marketing, debugging, documenting. What are the goals, short term, middle term, long term? What time scheme, what resources do they have. The company is very very silent the last months.

I am very positive about their results, and their ideas so far. But one cannot see any development going on until 'floops' there is something new on their website.

What also concerns me that there seems to be no connection with VFPX. Boyd&co are working on a VFP-IDE in Visual Studio, Etec already has it. VFPX delivers beautiful controls etc, but you can use the .Net-equivalents by using Etecs .netextender.
Energy is spilled. I'm accusing noone, I just wish we could centralize efforts. \

So to answer your central question: A suggestion is to open a special 'portion' of VFPX to commercial endeavours which are vital to the community, like Guineu and Etec.
That would keep things centralized and coordinated.

My 0.02 (euro's, btw)