XSharp Cahors 2.6a

Today we have released a new installer for XSharp Cahors 2.6a (aka 2.6.1), which contains several fixes for issues that our FOX subscribers have reported.

The what's new document describing all the changes can be found here:

{rsfiles path="general/Readme/whatsnew26a.rtf"}

{rsfiles path="fox/Compiler/XSharpSetup26aFox.zip"}

Unless some important problem is found in the next couple days, also the public version of the 2.6a build will follow shortly.
Thank you to all of you for your continued support and invaluable help in further developing the XSharp product!

Update on Saturday October 3rd:
Today we have updated the installer, and added 2 fixes to the compiler (PCall in a file name with an embedded dot was not working, parameter by reference with the @ modifier inside a codeblock was not working) and a fix in the runtime (callstack for errors in late bound code was sometimes not showing the method where the error originated).
We advise everybody to redownload the installer and install again. The files in the new installer are all dated October 2, 2020.

8 comments

  • Hi,

    When loading the solution with the new XSharp 2.6a (in VS2019), some project files (xsproj) were marked as updated by git. When comparing changes (menu "Compare with Unmodified ..."), there was no difference between the old and the new project file. Upon examining the issue more closely, I found that the project file that is marked as updated contains the version number 2.5.2.0. That is, the project version number has not been updated to 2.6.x. However, the file is marked as updated and is awaiting a commit command. On commit, git throws the error "fatal: unexpected sequence in commit output". I think this is due to the fact that there are no actual changes in the files.

    Best regards,
    Leonid
  • Hi Chris,
    Yes, I tried this option too. But after reload the solution (close VS and reopen) the problem persists. As a result, I just manually edited the version number in the xsproj files (replaced 2.5.2.0 with 2.6.0.0) and the problem disappeared.
  • I'm having the same issue as Leonid with the version changes, but I'm using Microsoft Team Foundation Server. Also, there are two more changes made when loading the solution in VS. Here are the additional changes:
    to

    This line was removed,

    I tried to undo the changes, but VS re-check out the project files. If these changes are correct, I can go ahead and check in the changes. Thanks.
  • [quote name="Boonnam"]I'm having the same issue as Leonid with the version changes, but I'm using Microsoft Team Foundation Server. Also, there are two more changes made when loading the solution in VS. Here are the additional changes:
    to

    This line was removed,

    I tried to undo the changes, but VS re-check out the project files. If these changes are correct, I can go ahead and check in the changes. Thanks.[/quote]

    My comment didn't appear here correctly. I will post it on the forum.