Progress Update Summer 2022

We think it is time for a progress update and a preview of what you can expect the rest of this year from us.

When What
End of July 2022 A new build X# 2.13 for our FOX subscribers.
This build will have some changes to the compiler, mostly in the area of the handling of DEFINES and numeric conversions and the /vo4 and /vo11 compiler options.
No real new features are planned for the compiler.
The runtime contains some fixes for FoxPro code and contains some small enhancements.
The VS Integration contains improvements in the formatting and intellisense, Windows Forms editor
End September 2022 We plan to release a new build (most likely called X# 3.0) that is compatible with .Net 5 and beyond.
This requires changes to the build system and VS integration and some changes to the compiler.
We will also additional compile the X# runtime for .Net 5 and beyond.
This build will also no longer be "binary compatible" with X# 2, so new versions of 3rd party components will be needed.
Of course we will still support .Net Framework 4.x
We also plan to release the first version of the VFP Xporter  that takes a VFP project file and converts that to a .Net solution.
October 2022 We hope to meet many of you during our X# summit in Memmingen.
And you can still register for this event.
We will also present a session on Virtual FoxFest about converting FoxPro apps to .Net.
December 2022 We plan to release the final version of the AnyCpu/Unicode VO Compatible GUI Classes and the AnyCpu/Unicode VO Compatible SQL Classes.
A first beta version of the X# SQL RDD is also planned for this month
These runtime components will be for FOX subscribers only.


  • It would be great if you publish 3.0 only when all 3rd party products are ready and add, together with the release report, the links to get those updates so we don't have to search how again to obtain every individual update. An X# SQL RDD looks promising. For us it is important that X# works better in VS, my most important issue is now the non working Immediate Window. I think that is far more important than supporting .Net 5. Do you have an idea how may users (end & programming) are using .Net 5? I couldn't find figures but if it's unknown, wouldn't it be a good idea to post a small survey? If the vast majority doesn't use it, then you could probably better concentrate on long pending wishes.
  • Dick,
    It is not either .Net 5 or VS improvements.
    You will have both.
    And even if the vast majority is not using it (yet), they will use it in the not too far future, I am sure about that.
    If you want to develop apps that work on non Windows platforms, you will need .Net Core / .Net 5.
  • IMHO it is not a good idea to publish version 3.0 only after all 3rd party products are ready. As long as it is clearly communicated, what works and what doesn't, everybody can decide if he/she want's to use the new version or not.
  • It does not makes sense to wait for the 3rd party publishers, but they should have access to an earlier version of v3.0 so they can prepare. The tools prepared by the X# team itself should be ready as fast as possible.
  • Hello Robert,
    I know that a lot is done with every new version, but at the same time I must conclude that working in VS has improved only slowly with some major functionality not working. As even your time is limited :) my idea is that a lot of users benefit from VO-like debug & Intellisense options while few users benefit from .Net 5 support. If, by end september, there is a first .Net5 supporting X# which is still miles beyond the debugging capabilities VO users are used to, I think you have pleased maybe 1 or 2 users at the expense of many other users. Or can we expect a fully functional, Ctrl X like Immediate Window with the option to inspect dbf values too, by the end of this month?
    One more question about this: Why .Net5 which reached EOL on May this year?
  • This is great update.Γö¼├í I will present this on our next budget meeting for next year.Γö¼├í I will make our FOX renewals earlier than that. We are supposed to renew last May 2022.Γö¼├í We have some critical delay in our end due to COVID19 stuff, but that is water under the bridge.Γö¼├í The constant publication of public free X# is really great, but you need some funds to move forward to greater heights.Γö¼├í I told my partners about it, as 50% of our system is written with X# and we need continue the subscription to get timely update.

    About third party: the only 3rd party that still haves compile warning is RightSLE with 33 9066/9071; while bBrowser for X# for 9021.

    I leave this warning alone because, it escalated so much that it may go out of control.

    About .NET 5.  It is already out of support.  This could mean as .NET 6.0 which is LTS, right? 

  • Count me as one of those waiting for it.

    I am forced to write my a .netstandard library to allow our X# core system be able to consume some of our code that runs on .NET 5 now 6.  Currently, X# does not support .netstandard.  Unless someone told me it can.

    Wishes* that longed to have with X# is VO-compatible GUI on .NET Core/5/6 and ready for testing with 7.

    .NET Framework is showing its age but it is rock solid but memory hog at most.
  • bBrowser may need to publish an upgrade and add some spices (new features) for minimal upgrade fee.Γö¼├í I am warming up to that idea.Γö¼├íΓö¼├í
  • Also note that the even numbered .Net versions have a longer lifetime than the uneven, which have a EOL in a bit over 1 year. Wouldn't make sense to target something to .Net5.Γö¼├í The Framework 4.8 had -yet- an unlimited lifetime , at least past 2030, see for a nice overview. Although some things of .Net5+ sound promising, I learned that everything that MS announced to be "the future" was abandoned or at least grossly neglected prematurely, e.g. The Windows Phone, WCF, WPF and much more. I understand you have no choice, not sure why not, because I would do everything I can to avoid Microsoft "this is the way to go" developments. My guess is that they won't even release .Net9 (due 2024) first because they have very few capable programmers and second because they have virtually no capable strategists and 3rd because it has always been like that. Within a few years Microsoft will recommend .Net Framework for which they will then release a 4.9 which does not really contain anything interesting new but it will probably support a new "design language" or something like that.