Microsoft has released several updates to VS 2019. The latest updates now properly support other languages on the New Project dialog:
So from now on we will support VS2019 for X#.
Microsoft has released several updates to VS 2019. The latest updates now properly support other languages on the New Project dialog:
So from now on we will support VS2019 for X#.
We had a first presentation of XSharp during the AtoutFox meeting in Lyon, France : May 23-24, 2019
http://www.atoutfox.org/
Current state of art, with different xBase "dialects" : Core, Visual Objects, Xbase++, VFP, ...
Many thanks to all members for their friendly welcome and all the help they offered in order have strong support of Visual FoxPro in XSharp.
It's time for a quick update about what we have been doing. Here are some things that we have worked on since the last build:
More news will follow soon.
The public version of XSharp Bandol RC 1 has also been released. Click here to download it (you have to login first):
XSharp Cahors 2.20 Public Installer
Popular 2.20.0.3 XSharp Open License 64.89 MB |
2024-06-13 |
We are very proud that we can announce that we have released X# Bandol RC 1 to our FOX subscribers.
A public build of this product will follow shortly.
This build has completed the VO and Vulcan compatible runtime.
Unfortunately we found some last minute issues in the DBFCDX driver which could corrupt your indexes. We have therefore decided NOT to include the DBFCDX driver. An update for this will follow in a few weeks.
Some of the highlights of this build:
new IS Pattern expressions:
IF <variable> IS <type> VAR <newvariable>
This automatically creates a new variable <newvariable> that is only visible in the scope of the IF expression.
We have also added extended support for the & operator in combination with the Alias (->) operator and made a change to the preprocessor to make it more compatible with Xbase++. You can now use
(nArea)->&(Expression)
to read a field from a workarea where the fieldname is in the expression. Of course you can also use
(nArea)->(FieldGet(FieldPos(Expression)))
which is almost what gets generated by the compiler.
There are many larger and smaller changes in the runtime to make it more compatible with VO and Vulcan.
There are also some changes in the Visual Studio integration, such as:
FOX Subscribers can download this new build here:
{rsfiles path="fox/Compiler/XSharpSetup2RC1Fox.zip"}
Page 34 of 57