XSharp Cahors 2.21 - Installers available

Today, we have released the installers for XSharp Cahors 2.21.

The "What's New" document, describing all the changes, can be found here:

XSharp 2.21 what's new
Popular 2.21.0.5 416.58 KB
2024-11-25

The public installer can be downloaded here:

{rsfiles path="installers/XSharpSetupPublic2.21.0.5.zip"}

 

 


11 comments

    • Markus, indeed, I see a few errors, but those are actually warnings. Please disable the treat warnings as errors option in the project options (Build page) and it should compile now. Will also ask Fabrice to take care of the warnings.

  • Hello,

    Every time I start our solution after updating to X# Runtime 2.21.0.5, I get the following message from Visual Studio and the connection to the source code management for each X# project:

    “This operation cannot be completed. You are trying to move or rename an element in source control even though an element with that name already exists, the element is exclusively locked elsewhere, or the element path is invalid.”

    We work with a Microsoft DevOpsServer / TFS, if all messages have been confirmed with OK, the individual projects are loaded, it compiles but all project files *.xsprj are checked out but no change can be detected. It only affects the X# projects, C# projects that are also contained in the solution are loaded properly. It looks as if a file is renamed during loading, but I cannot determine which file it is. The help behind the help button does not help either.

     

    Message.jpeg

    • Christian,

      - Are you sure your project files are named *.xsprj  and not *.xsproj (note o before the j)?
      - Do you have .bak files with the same name as the project files in your project folder? If so, can you remove these and then try again?

      Robert

  • Robert,

    sorry, a typing error, it should be .xsproj.

    There are no *.bak files in the project directories.

    Christian

  • Christian,

    When you open an existing project with X# 2.21, then our project system tries to update the project files and add some properties that contains default values that were "enabled" in the past.
    I suspect that this causes problems in your situation.
    Can you try this:

    • Copy the solution to a folder where it is not under scc
    • Open the solution and let the project system update the xsproj files
    • Then copy the changed xsproj files to the folder where they are under scc

    Alternatively you could try to checkout the xsproj files manually before opening the solution, so all files are already read/write

    Robert

  • Robert,

    yes, updating the project files is the problem. The easiest way to fix this is:

    1. open the solution and acknowledge and ignore all errors
    2. open the properties of the individual projects, make any changes so that they are saved safely and save
    3. undo the unnecessary change and save again and or close

    The project file has been corrected.

    Christian