Progress Update January 2024

First of all, we want to wish everybody the best for this new year.

Then, we would like to inform you about our progress:
We are busy finalizing build 2.19 of X#. This build will fix some issues that were reported and adds some new features.
There are new features in the compiler, VS integration and runtime.
One of the things that we have added, is support for some FoxPro embedded SQL statements, such as CREATE CURSOR, CREATE TABLE, ALTER TABLE and INSERT.
Other embedded SQL commands will follow in a next build.
We expect to release 2.19 to our beta testers in week 3. Then, when things go as planned, we should be able to release build 2.19 in week 4.
The preliminary what's new document for this release can be found here

During our presentation in Memmingen, we have also announced some other changes.
Let's summarize these here with some expected release dates

Feature Scheduled release Note
X# SQL RDD Beta: Early February
Release: End of March
This will be a separate product.
XGUI Classes Beta: End of February
Release: May
This will be a separate product.
X# 3.0
includes VS Project system support for .Net Next
April-May For everybody.
Designing Windows Forms for .Net 5 and later inside Visual Studio will be difficult,
because of changes that Microsoft made to the Windows Forms Designer
We will also make some breaking changes to the X# runtime in this build.

We are also planning another X# summit 2024. We have reserved accommodation in the HYPERION Hotel in München (Munich) on October 17-18. More information about this will follow in a few weeks.

Finally, we will move this website to another hosting provider later this month. We hope that this will not cause too many hickups. The website itself will not change, only the location where it is hosted.

 


8 comments

    • Karl,

      Separate product means that it is not automatically included in FOX. There will be a discount for FOX subscribers.
      The idea behind this is that we do not expect that all FOX subscribers will need this.

  • Awesome update, I can't wait to get full intellisense on winarm !

    Regarding XGUI Classes, any chance that bbrowser will be supported or still out of scope ?

    • Basil,

      Wolfgang has communicated with Joachim Bieler from bBrowser. He told that he will take a look at this. We have also offered to help him with the conversion.
      But that will most likely also not be a free update. There is quite some work to do, to move a component like bBrowser to Windows Forms.

      Robert

  • Could you explain your comments "Designing Windows Forms for .Net 5 and later inside Visual Studio will be difficult /  We will also make some breaking changes to the X# runtime in this build" a bit more?

    The way I read it is that using X# 3.0 will be about impossible to use if you use Winforms. Or do you mean in general anything else than .Net Framework (so .Net5 and higher) should better be avoided if you use Winforms?

    And what do you mean  with "breaking changes"? In the meaning of a breakthrough, something which could be good, or in the meaning that using X# 3.0 breaks existing code?

    Dick

    • Dick,

      Breaking changes means that 3rd party products need to be recompiled to work with X# 3, for example because the prototypes of some of the runtime functions will be changed.

      The issue with the Windows Forms Editor in VS 2022 is too complicated to answer in a comment. We have some ideas and we will come with a solution.

      Robert

  • Thanks Robert,

    Very much looking forward to X# 3.0 when it comes. 

    And to joining your guys in Munich!

    Fergus