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

JNetReflector raises an issue can be correlated to FAST_FAIL_SET_CONTEXT_DENIED #582

Closed
masesdevelopers opened this issue Dec 21, 2024 · 2 comments · Fixed by #583, #584 or #585
Closed

Comments

@masesdevelopers
Copy link
Contributor

masesdevelopers commented Dec 21, 2024

The workflow runs on windows-latest which is equipped with .NET 9 and, as stated in masesgroup/JCOBridgePublic#7 (comment), the executable shall be compiled avoiding CET. However it is a strange and unexpected behavior since JNetReflector builds only for .NET 8 (<TargetFrameworks>net8.0</TargetFrameworks>) which is not affected from enabled CET. Try to execute the same workflow with the following options
image
to verify if the problem is raised from the executable itself.

Meanwhile an issue will be opened on JNet

Originally posted by @masesdevelopers in masesgroup/KNet#820 (comment)

@masesdevelopers
Copy link
Contributor Author

Remove the condition in

<PropertyGroup Condition="'$(TargetFramework)' == 'net9.0'">
so every supported framework will be CET aware.

@masesdevelopers
Copy link
Contributor Author

Since the CET is applied at process level and dotnet tools installation creates a specific application cannot be managed from us, the documentation shall be enhanced to report the last changes made masesgroup/KNet#820 (comment) both on JNetReflector and JNetCLI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment