You can take the resulting IL and disaasemble into C# code.
The X#/vfp code can be viewed as syntactic sugar on top of a C# library.
This C# lib is base on the expirience of coding a Clipper lib...
The C# disassembled code is not totally lousy.
Been there, nosied about that
;-)

>Yep. The toher thing to consider - once it is actually finished (if ever) - is just how practical it would actually be in the real world. One of the problems with VFP is that no one wants in, it part because there are so few VFP developers - and it seems to me you would have a similar problem with xsharp. My boss would not be to keen on the idea of moving from one technology that they have diffulty finding help with to another obsucure programming language. At the end of the day it seems that C# plus SQL Server is probably going to be the way to go for now.
>
>
>>Hi Victor,
>>
>>it definately is something to watch - I started as eager beaver in 2019.
>>Did a bit of coding, documenting the scope, tried to explain vfp.
>>I was stoked at their roadmap with pareto 89% done within a year.
>>
>>They missed by a mile - and what for me is worse, they did not get
>>what at least I consider vfp special sauce of buffering tables plus
>>tableupdate/-revert, getnextmodified, getfldstate, old/curval, get/setfldstate
>>which are also the backbone of views and cursoradapter generated local tmp tables.
>>SQL on dbf tables to be accessed by driver, "cursor" only in name
>>as memory list of ADO.NET ilk, to be accssed not via SQL but LINQ.
>>
>>Unclear if/when/scope of code accessible in mobile or WASM would be.
>>Also, speed of vfp table handling was not there - might be reached.
>>
>>As they do not offer the things I mentioned/hope for as vfp sauce, I might hack a bit
>>on SQLite in mobile, which Google offers also in WASM as replacement to WebSQL.
>>
>>It gives you option of SQL into your local cursor of unpersisted data,
>>offers some local persistence, potentially allows you to decide on memory or disc storage,
>>might even offer RO access from a local database for offline first.
>>
>>xSharp is interesting (and educational, if you read their open source),
>>but currently it does not offer even similar capabilities (see special sauce)
>>and it is unclear if my targets "web SQL local storage/engine" or mobile
>>will be in reach within few years.
>>
>>Specc your targets above current vfp (with additions from FoxInCloud plus Rick for
>>web FoxIncloud is based on and perhaps a replacement for WebBrowser via WebView2)
>>try and measure, then decide... The crew definately is competent and helpful
>>but they have not realized what large vfp apps need (from very personal POV).
>>
>>regards
>>thomas
>>
>>>This has nothing to do with Python ... but I am interested to see how this goes -- its' bascially a .net verson of VFP. I have not tried it yet and don't know if it's even usable yet.
>>>
>>>https://www.xsharp.eu/