Guys,
I checked an old Vulcan installer, and the help file contains 2 samples
- HostingVOWindowSample.zip
- VOWinFormAppSample.zip

Maybe we can adjust these for X# and include them in the next Help file. I will see what I can do. Robert

Dick,
Yes, a Goto can fail when there is an index issue.
The RDD tries to locate the "current" key in the index when you do a Goto.
Robert

Volkmar,

A quick first test shows that our installer detects this version (it identifiers it as Visual Studio 2022 Enterprise (18.0)) and the extension is installed correctly.
The Edit / Compile / Debug cycle also seems to work.
Our debugger windows (Globals, Publics/Privates, Workareas, Settings ...

Rob,
The file you attached is encoded with the US_DOS codepage (437).
The file does not have the Ansi flag set in the header (the first byte is 0x83 and not 0x87)
The DBFNTX driver checks the Ansi flag in this header.
If your app runs with SetAnsi(FALSE) then the file is read correctly. The value of ...

Volkmar,
Thanks for pointing at this.
We will of course make sure that our VS integration works with VS 2026 as well.
Hopefully that did not make too many (undocumented?) changes.

Robert

Thomas,
The [NeedsAccessToLocals(TRUE)] attribute is only effective when compiling in the VFP dialect.
The function Evaluate(cString) is in the XSharp.RT assembly and not compiled in the VFP dialect. So its single local cString is not pushed to the list of locals. You can see that if you decompile ...

Rob,
Your DBF is an OEM file (0x83) with the US MSDOS codepage (byte 0x01 at 0 based position 29)
What is the DOS codepage on your machine?
And can you send me the DBF for inspection?

Robert

Rob,
There is a HUGE difference between how VO and X# in this area (with the DBFNTX driver)
VO checks the first byte of the DBF. If that byte is 0x03 or 0x83 then VO assumes the bytes are OEM characters and converts these to Ansi in the current codepage.
When the first byte ix 0x07 or 0x87 then VO ...

I would like to thank everybody for their suggestions.
I had hoped this discussion would focus a bit more on the organization behind the XSharp product and a bit less about the subscription model. But we have heard your comments and will see what we can do with them.

Robert

Jamal,
We have not worked on this yet
.net 9 compatibility is on the list for x# 3.

Robert