Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ScriptEngine.EnableDebugging #209

Open
babblefish99 opened this issue Nov 1, 2021 · 3 comments
Open

ScriptEngine.EnableDebugging #209

babblefish99 opened this issue Nov 1, 2021 · 3 comments
Labels

Comments

@babblefish99
Copy link

babblefish99 commented Nov 1, 2021

Hi Paul,

I've just upgraded to the latest version of Jurassic (3.2.4) and have found that EnableDebugging has been removed from the ScriptEngine Interface.

Has debugging of scripts been removed from Jurassic or is there another way that I should use so that I can debug scripts when using ExecuteFile?

Many thanks for any info
John

@paulbartrum
Copy link
Owner

Prior to the 3.2 release there was a .NET 4 specific build included in the Nuget package, which included the debugging functionality. I dropped support for this in the 3.2 release because it's a bunch of work to maintain and there shouldn't be too many people still using .NET 4. Unfortunately .NET core has never supported the necessary functionality to implement debugging (https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.symbolstore.symdocumentwriter?view=netframework-4.8).

@paulbartrum
Copy link
Owner

The only straightforward way to keep the debugging support is to stick with the 3.1.0 version I'm afraid. Sorry!

@xlljc
Copy link

xlljc commented Dec 20, 2021

The only straightforward way to keep the debugging support is to stick with the 3.1.0 version I'm afraid. Sorry!

That's too bad. Do you have another way to implement debugging?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants