Thanks for the reply Ken.


>I don't know what happen to the .NET compiler project, either all the functionality needed wasn't able to be done, or not enough profit in the business model for it, or both. In any case, I do not think the best way to build .NET based applications is to use a FoxPro based syntax compiler, since I don't think it will match the functionality of VFP native, nor include all the functionality that C# or VB.NET offers. I have no interest in .NET, and my focus is on Servoy now since IMO it's a far better developer platform for data-centric client and web apps, and much more like VFP.
>
>Microsoft created IronPython and IronRuby, then dropped support and gave it away to the community. Most developers who move to .NET end up realizing the best language to use (and invest in) is probably C#, followed by VB.NET. The other .NET languages will never get near the support or evolution of functionality. Microsoft created J# targeting Java developers programming on .NET, and nobody used it, they all ended up learning and using C#.
>
>I don't think there is much profit in .NET tools, compilers, or runtimes targeting VFP developers, and those projects appear more like hobbies than real businesses - which is not something most developers would want to build a real line of business application on. These are just my own opinions, and I respect others who think otherwise in this area and I'll be curious to see where it all goes for these related efforts.
>
>>Thank you for posting the details of what we all guessed was going on behind the curtains.
>>
>>One good reason VFP was not strategic for MS is that it did not provide it with any licensing income after the developer licenses. In other words, it provided no CAL income. It would have been better for the VFP comunity to pay distribution licenses than loose the language's continued evolution. We were penny wise and pound foolish. Not that it was our decision.
>>
>>It was another missed opportunity that "Samuel David" was not able to finish his .NET compilable version of the VFP language. I was hoping someone with the strategic need to compete with MS, such as Google, would purchase that code and make it open source under the able stewardship of someone such as yourself (hint). I'd buy an annual suscription to support that project.
>>
>>Why don't you talk to "Samuel David" and see what can be done? I believe I know how to get in touch with him.