The plans they are changing

Until now, we have told you that X# 3.0 will be for .Net next and that X# 3.0 will be the next release after 2.15.
Some of you have told us that you think .Net next is less important than some other things that we have on our to-do list.

We have discussed this and decide to listen and change our priorities.
Not that .Net next is very difficult w.r.t. the compiler and runtime, but full support inside Visual Studio takes a bit longer than we expected.

We will therefore work on several other things first that many of you have asked for:

  • RDD on top of SQL (through Ado.Net)
  • Client/Server RDD, where the server connects to the database, and the client can only access the data through the server (like Advantage does).
    The server could then use normal DBF files, but also a single user SQL database, like SQLite or a normal SQL database.
  • Completion of the Unicode/AnyCPU GUI and SQL classes for VO users,
  • Completion of the converter and runtime classes for FoxPro users,

Our original plan to drop support for Visual Studio 2017 after X# 2.15 is still in place. In the build after X# 2.15 we will deliver a VSIX file with the Visual Studio integration as we have in X# 2.15 that you can keep using with VS 2017.
New development in the Visual Studio integration will be for Visual Studio 2019 and later.

The upcoming build 2.15 is being tested in the team. We expect to release it to our beta testers next week. Hopefully we can release this "Carnival build" to our subscribers in around the 20th of February..

 

19 comments

  • Great news Robert - the Client/Server RDD to replace Advantage and the Unicode/AnyCPU GUI and SQL classes would be very beneficial in ensuring an upgrade path for our applications.
    thanks for your continued work and awesome on X# !
    cheers
    Trevor
  • A lurker here... The focus on the RDD is something that would motivate me to transition to this environment from Harbour, sign up for the pro subscription, etc. Good luck with the development work.
  • Ian, this will only be a few months' delay, it's not like we don't still have it very high in the priority list. It's just that dealing with all the quirks and complexities of Visual Studio integration (which is the only thing still preventing us from fully supporting the newest .Net versions) every day, almost all day is absolutely exhausting... And since also many people are asking for other features, we will take a break, work on them for some time and then return back to Visual Studio matters. Btw, it's not like ALL of the mentioned features are being pushed forward now, many of those items we had been already working on them (by different dev team members) already anyway, in parallel with VS integration for .Net next and more.
  • "(which is the only thing still preventing us from fully supporting the newest .Net versions)" - if so, we could use it in Xide? Then you might consider releasing it w/o the VS integration ;-)
  • Karl, that should be working already, since months ago! I haven't tried it myself, but if you select the appropriate references (instead of those in the .Net 4 GAC) in a regular XIDE app, then I see no reason why it shouldn't work. The compiler does support .Net 5,6,7 since a long time now.

Main menu

  • Buy
  • Contact
  • Free software