More than a year ago, we have published our first development Roadmap for the X# project. This new roadmap continues the tradition and describes what our plans for 2017 are.

Click here for a PDF with this document which also looks back at what we have achieved in 2016

Our plans for 2017

You will not be surprised that the open items from our roadmap for 2016  are still on the to do list for 2017. Some of the things on our to list:

  • Improved Visual Studio support:
    • Nuget support
    • Editors for the VO Binaries
    • Support for other VS subsystems, especially those that are based on T4 templates.
    • “Intellisense” features for the editor, such as completion lists, parameter tips, Goto definition etc
    • Class browser and Object browser support
    • Debugger support for Globals and X# expressions

  • Create the X# runtime, so you no longer need the Vulcan Runtime to run your apps that use RDDs and the VO SDK classes. Our intention is not only to replace the Vulcan runtime, but also to improve it.
    After all, we have done this before, so we can do it again, but then better!
    • Thread Safe runtime and RDD system
    • Runs on AnyCPU
    • Support Runtime Macros AND scripting (our macro compiler will support the complete language!)
    • Portable where possible. Unfortunately, there are many areas (IO related mostly) that can’t be completely portable

  • Add support for an extra xBase language. At this moment, we are considering to add support for (x)Harbour. The (x)Harbour community is very active and seems to be the most interesting target audience.

Contents / Motto

April 2017

Spring 2017

Most “intellisense” features in VS
X# Scripting/Macro support
First version of the Runtime

July 2017

Summer 2017

Complete X# Runtime

October 2017

Autumn 2017

First version of (x)Harbour support

Christmas 2017

Winter 2017

Complete version of (x)Harbour support

Michael Hagl
Hi Robert,

the RDD plans sounds very good (there is also a world outside of SQL)

The best news IMHO are to hear that you plan to support xHarbour language. I'm using xHb since 2010, but I don't know how to help, because I'm an aplication developer without skills in C (parts of xHb are written in C), but perhaps I can contribute to help a litle bit.


Robert van der Hulst

We do not need developers that know how to code in C. We need developers that know how to code in XBase.
We strongly believe that the best way to create a successful product is to use that product yourself.
Of course it useful if you can read C.


Richard Wooters
Hi Robert,

What will be the difference, if any, between X# RDD and Vulcan.NET RDD?

Richard Wooters

Robert van der Hulst
Richard Wooters said :
Hi Robert,What will be the difference, if any, between X# RDD and Vulcan.NET RDD?

There will be many differences:
- The RDD system will be completely managed code (unlike the CDX driver in Vulcan)
- We will support all known field types (for example also the FoxPro extensions such as DateTime, Integer and autonumber)
- The RDD system wil be thread safe. Each thread will have its own RDD State such as Current workarea and its own workareas
- X# will include an Advantage RDD
- The RDD system will be written in X#


Rene J. Pajaron
This is exactly I want to read. X# coded RDD for both Cdx and ADS.

However, it will be available only at the middle or probably year ender.

Robert van der Hulst
Yes most likely Visual Foxpro will be next.
But you do not have to wait that long: our RDD system, which is part of the Runtime, will support FoxPro DBF files including all FoxPro specific field types and FoxPro CDX files from day 1


neeraj charne
Visual foxpro will be next ? rolleyes
Hide comment form

1000 Characters left