You may remember that I had to drop back to using version 1.02 with 1.03 update a little while back. For the weeks after uninstalling 1.1 I had VS 2015 working without real issues and did a lot of work on my conference material for Cologne 2018. No probs !
However, now that 126.96.36.199 is available I am having another go / effort at moving forward.
I will keep details / notes on any issues I see - for you, and report them back.
At the moment things seem pretty good - BUT - I have not done a lot of things so far today - so fingers crossed, all 9.5 of them ;-0)
Glad to see that Greek guys have a sense of humour ('ice') when Dutch guys don't it would seem ;-0)
After a lot more testing and general use I have to say that the 188.8.131.52 version is working very well in WPF apps, as far as I can tell to date.
It is noticeably better and superior to the previous version - for what I was doing.
However, by pure chance a few minutes ago I think I have discovered a small issue. Possibly?
The following image shows that I have Case Sensitivity set 'ON' - this is because I got used to C# over a few years and liked the idea.
However, when I noticed some working code in an image I made for my eNotes and material for Cologne 2018, I see the following on lines 47 and 52 :-
Have I misunderstood what Case Sensitive means ? I thought I should get a compiler error because I have 'f' and 'F' - but the app compiled and ran - and give the right results.
The casual Forum readers may notice that the .NET code in X# syntax seems very modern in many respects. Yes, just a few lines doing me a useful job, and yet we have many variations of how to declare a local variable, WPF data binding, LINQ query statement using an Anonymous Type and the VERY useful 'Let' clause allowing some string handling / processing, within the query statement.
Obviously this code is using Collections.
It is so GREAT to see that this can all be done in the latest X#, I am VERY impressed with what we can do, and the general look / feel of X# syntax coding at this end - yes, it all works even in Wales, UK.
Some pointers on the Case Sensitivity would be NICE ;-0)
It's what Wolfgang said, case sensitivity is not implemented yet, that's why it's grayed in the project properties window. It's not trivial to implement that, and we have some other items in the todo list (see: x# runtime!) that have very high priority, so I am afraid it will have to wait a bit.
Thanks for your feedback about the rest, glad X# is working well for you.
BUT - that means I may have a few error to correct in the future ;-0)
Have a nice weekend.
P.S. if anyone is interested to know what I am doing, then it is for a section of the eNotes on using Reflection to examine Assemblies, to find Enums in the first instance, and then be able to select any Enum from any chosen DLL and see the options for the Enum selected.
Obviously I an also looking at Enums from a Framework, and personal business app point of view. In doing this research I am trying to code the way I will be presenting material in X# syntax at the Cologne conference in April 2018.
Needless to say I am learning a LOT !!!
However did I manage without LINQ - thanks Nick for the encouragement
Reflection is a great thing - I'm using it in some places when I do late binding or other "strange" things like this one (from one of my TextBox subclasses that implement a similar "value" behaviour as the VO singleline edit):
(using an image because the code will be released later with a sample)