We have just released XSharp "Anjou" Update 1.

This update fixes some issues that were found in the last week:


  • Fixed a problem with VERY old versions of the Vulcan Runtime (early Vulcan 2 versions)
  • Variables declared as DIM Byte[] and similar are now Pinned by the compiler
  • [Return] attribute was not properly handled by the compiler. This has been fixed
  • Compound Assignment (u+= f or -=) from USUAL and FLOAT were causing a stackoverflow at runtime caused by a problem in the Vulcan Runtime. These expressions now generate a compiler error with the suggestion to change to a simple assignment ( u := u + f)

Visual Studio Integration

  • Project References between XSharp Projects were also loaded as assemblyreference when resolving types. This could lead to speed problems and unnecessary memory usage
  • Improved the speed of the construction of Completion Lists (such as methods and fields for a type).
  • We have also added Completion List Tabs, where you can see fields, properties, methods etc. on separate tabs. You can enable/disable this in the Tools/Options/Text Editor/XSharp/Intellisense options page.

VO Xporter

  • We have added a check to make sure that the default namespace for a X# project cannot contain a whitespace character

On behalf of the Devteam I want to thank you all for the nice feedback that we got in the last week.This is really appreciated !


#15 Wolfgang Riedmann 2017-07-15 19:08
Thank you very much! So we can expect an Idefix or Asterix release sometimes in the future. I like the Asterix and Obelix stories!
#14 Robert van der Hulst 2017-07-14 16:38
Maybe it is time we tell them about the battle of Anjou in 42 AD, where the Gaul Fabrix Fortix beat the Roman general Brutus HomusCampus, which was the inspiration for Goscinny and Uderzo for their famous strip books.

#13 Rene J. Pajaron 2017-07-14 03:13
Quoting Wolfgang Riedmann:
Only for curiosity: Why is the release called "Anjou"?


a former province of western France, on the Loire River. It was an English possession 1154–1204

This is what Bing told me.

#12 Fabrice Foray 2017-07-13 18:33
Well, an answer could be that it has been decided during XBase.Future 2017 in Köln, but it would not explain the "Why?".
May be, we should wait for the next release to see if the name is random, or on purpose ;)

#11 Rene J. Pajaron 2017-07-13 03:01
I cannot resist: our banking software is stuck at 6.x.x due to the government certification we filed is at 6.x.x.

So we are now in 8 generation, I am still wrote it as Version 6.6.x which supposed to be in 8.x.x if I followed by habit in versioning system.

There it goes.... I do not want another certification process, but probably I will drop versioning altogether?
#10 Chris Pyrgas 2017-07-12 19:11
I am not sure if I am allowed to say! And if I am, I still don't know exactly the answer :-)
Let's see if Fabrice or Robert will step in here..
#9 Wolfgang Riedmann 2017-07-12 17:16
Only for curiosity: Why is the release called "Anjou"?
#8 Chris Pyrgas 2017-07-12 14:25

#7 Karl Faller 2017-07-12 14:14
Quoting Chris Pyrgas:
OK, I guess it would had been better to simply admit that we indeed used way too many subversion numbers
Now that's true greatness! ;)

#6 Chris Pyrgas 2017-07-12 14:01
Nah, the final dot in the version number is actually the decimal separator! So in decimal notation that would have been 1.0.1,5

OK, I guess it would had been better to simply admit that we indeed used way too many subversion numbers, but I could not resist :-)


You need to login to post comments on this website.