Wolfgang, I know of one customer that is running a Mac on Arm and is running Visual Studio for Arm on that machine. We have added ARM support for the X# intellisense in Visual Studio (a special version of the SQLite driver). Part of our VS integration (the code model and the editors for VO forms, se...

Just like you can pass the dialect from the command line, then you can also add these references from the command line:

This assumes you have added these DLLs to the GAC.


Robert

Guys, The Windows codepage 1250 has most eastern european characters and umlaut characters: https://en.wikipedia.org/wiki/Windows-1250 If your DBF has the codepage byte 0xc8 then you should have no problem saving these characters. I am not sure how you are checking if this succeeded, but if you're u...

X# interactive is not really meant to work as a FoxPro command prompt, if that's what you're looking for.
It is the X# equivalent of C# interactive, and mostly works in the Core dialect.
What are you trying to achieve?

Robert

Dick, Maybe some extra clarification: The "AnyCPU" in the top toolbar is the name of the current platform for the solution as a whole. The "Debug" and "Release" are called Configurations. Inside a project file you will see sections like the following: <PropertyGroup Con...

Peter, DBF files can contain only characters from the codepage that is in the DBF header. That codepage is at (zero based) byte 29 in the DBF header. You can find the meaning of the values in the following file: https://github.com/X-Sharp/XSharpPublic/blob/main/src/Runtime/XSharp.Rdd/Enums.prg If th...

Dick,

Platform Target is the determining factor.

Robert

Dick, There are various possible scenarios which, need different solutions: .Net Framework: - AnyCPU and X#: VS2017, VS2019, VS2022 (internal form editor) - 32 bits and x#: VS2017 and VS2019 - 64 bits and X#: VS2022 (internal form editor) - AnyCPU and C#: VS2017, VS2019, VS2022 (internal form editor...

Mike,

Some winforms apps cannot be designed with VS2022, but there should not be a problem running the app in the debugger.

Robert

Mike,
We recommend that you use VS2022 for this scenario.
We made some significant improvements to the X# debugger that only work with VS 2022 and not in VS 2017.

Robert