The XSharp development roadmap for 2019

In this article we would like to share with you our development roadmap for the coming months.
We are now reaching  the final stage of the development of the runtime for VO & Vulcan and we are looking at new things that you an expect the coming year.
In the coming weeks we will release the first Release Candidate for the XSharp runtime. After that we expect to need a few weeks to finish the final remaining issues.
The schedule show you what we have planned to do after that.

The schedule below of course is an indication and as always: no guarantees.

Component Start Completed
XSharp 2.0 Release
- Runtime
- RDD System
- VO Class libraries
  May 2019
ReportPro 2 & 3 for XSharp 2.0 April 2019 May 2019
Xbase++ runtime functions   July 2019
(Visual) FoxPro dialect, including runtime functions
and support for VFP DBC and VFP datatypes in the DBF format
and a VFP - X# +Visual Studio converter
April 2019 August 2019
VO GUI and SQL Classes with Unicode and AnyCPU support (on top of Windows Forms and Ado.Net) June 2019 August 2019
VFP UI Classes August 2019 October 2019

As you can see in the schedule above: we have not planned to do Xbase++ UI classes yet. We need a business case (someone with a business app that uses the Xbase++ UI classes) or someone that can help us to define what exactly is needed to do this.

If you are missing something in this schedule, or if you want to help to implement / add something, please let us know. We welcome your input.



  • Please don't forget VO DBF classes with Unicode and AnyCPU support to work with the VO GUI classes based on Windows Forms.
  • Wolfgang,
    I am not sure what you mean. The VODBF classes are already Unicode (of course the DBFs are not) and ANyCPU is not a problem for DBF as well. We are doing nothing in these classes and in the underlying RDD layer that will not work in AnyCPU.

  • Hi Robert,
    if the current VODBF classes will already work with the new VOGUI/WinForms classes, this is fine.
    I'm looking forward to these classes, even without a bBrowser.
  • Some VO programers use bBrowse and FabOutlookBar, like me. If we will have and, should X# compile them?.
  • Ramazan,
    Yes, if you have the source of these you should be able to recompile them for the X# Runtime.
    We DID find a problem in various versions of bBrowser, so you may have to fix a few lines of code (this has to do with calling managed functions through PCall()) But apart from that you should be fine.

  • Hi Robert,

    My suggestion:

    Upon release of XSharp 2.0 (Runtime, RDD System, VO Class libraries) and ReportPro 2 & 3 for XSharp 2.0; prioritize VO GUI and SQL Classes with Unicode and AnyCPU support (on top of Windows Forms and Ado.Net). This is much needed to existing Vn and X# users (me included).



  • Wolfgang,

    [quote name="Wolfgang Riedmann"]Hi Robert,
    in your list the port of VO2Ado to X# is missing, and a port of bBrowser.NET.
    bBrowser is a product from Joachim Bieler. We can't promise anything in that area.
    Vo2Ado is a product from myself but does not "belong" to the X# project. That is why I did not mention it here.
    I can say that I will create a Vo2Ado version for X#.