@litdev,
thanks for the tip. I tried it straight away with the Chessengine program that operates the console and the graphics and of course it failed.
It's like exporting to VB.NET. Source code and a project file are created, but how do they fit into the development environment (in this case VS 2017). Small Basic seems to be somehow more error-tolerant than the VS languages.
That's why I think that the C# source code that is created directly from the SB source code should be cleaner and easier to port to the new development environment. Especially if it has already been converted to an SB exe as C#.
I'll show my failed attempt in another thread so as not to stray from the topic of Open Small Basic: https://litdev.uk/mybb/showthread.php?tid=148
thanks for the tip. I tried it straight away with the Chessengine program that operates the console and the graphics and of course it failed.
It's like exporting to VB.NET. Source code and a project file are created, but how do they fit into the development environment (in this case VS 2017). Small Basic seems to be somehow more error-tolerant than the VS languages.
That's why I think that the C# source code that is created directly from the SB source code should be cleaner and easier to port to the new development environment. Especially if it has already been converted to an SB exe as C#.
I'll show my failed attempt in another thread so as not to stray from the topic of Open Small Basic: https://litdev.uk/mybb/showthread.php?tid=148