In a very similar situation like yours (using jint and wanting users to debug their scripts in VS Code), here are the solutions I've found:
Quick fix
Simply launch the code using npm, as VS Code is already equipped to handle debugging through it. It requires npm to be installed and added to the path, which is fairly standard nowadays.
Detailed approach
Utilize
Jint.Runtime.Debugger.DebugHandler
to better integrate with VS Code.
This method ensures consistency across different runtimes without any issues.
However, it does demand a significant amount of effort for just minor enhancements. Despite being well-crafted, Jint's documentation falls short even for open-source norms.
Incorporating dotnet can complicate the cross-platform support. The challenge lies not in running executables on various platforms or requiring diverse runtimes, but rather in deployment. Ideally, a polished solution would involve a VS Code extension handling the installation and setup of platform-specific dependencies. While you could manually manage dependencies as in the quick fix, it somewhat diminishes the benefits of the detailed approach.
There is also a risk that this method relies on unfinished work - refer to https://github.com/sebastienros/jint/issues/674#issuecomment-735478529