Hi Basile, I was not aware of that, thanks! So the (roslyn) compiler can be setup so that it does not even allow assigning null to "regular" reference types! But when I try this in X# LOCAL c AS STRING? c := NULL the compiler reports "warning XS8632: The annotation for nullable reference types ...

Hi, What's the exact code you are using to call the method? Btw, using "STRING?" to denote a nullable string is not correct, the STRING type (System.String) is a reference type (like ArrayList, Form etc, or any class you define with the CLASS statement), so it is already possible to assign NULL for ...

Hi Richard,

Do you mean those features do not do anything at all anymore? Or are not even available as commands at all?
Could be related to a recent update in VS 2022 where MS did some breaking changes (without giving a heads up), but this should be solved in the upcoming X# 2.21 release.

Hi Irwin,

Thanks, both issues are fixed now, will add a few more things that I'm working at and will send you an updated version.
Btw, there's also a context menu command "Delete All" for the Watch window.

Hi Horst,

Did you check the "Reg Exp" checkbox in the find in files dialog?

Hi Karl & Horst, Ah right thanks, in that case, that's what regional expression searching is for. If you don't want to learn how to construct regional expressions (I don't and don't want to!), that's one of the few usages of AI that I like, you can ask it "Get me a regional expression that searches ...

Hi Horst,

Sorry, I did not understand what you mean. Can you please give me an example?

Guys, Yes, it should be possible to use classes from VOInternetClasses.dll in a VFP dialect app, I don't think this library depends on anything that's specific to the VO dialect, so it should be no problem. But I think there's no reason to do this. This library is provided simply for compatibility ...

Hi Horst,

Well, VO is extremely weird at times

I agree, it does not make much sense, but we had to implement it the same way as in VO, otherwise it would certainly break existing (ported to X#) code.

Hi Horst,

It's not a bug in the sense that this is how VO works, too, with the partial equality operator when there's a usual involved.

If you want to test for absolute equality, you need to use the == operator. Or you can turn SetExact(TRUE).