generateclasses.yaml does not work with latest JNetReflector

[masesdevelopers]

Describe the bug
Running generateclasses.yaml workflow the error 0xC0000409 (exit code -1073740791) is raised

To Reproduce
Steps to reproduce the behavior:

1. Go to generateclasses.yaml action
2. Run the workflow
3. Wait execution
4. See error

Expected behavior
The workflow shall run without problems

Screenshots

Desktop (please complete the following information):

• OS: Windows GitHub runner
• Version: commit 3fe193a

Additional context
Previous version works

[masesdevelopers]

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

to verify if the problem is raised from the executable itself.

Meanwhile an issue will be opened on JNet

[masesdevelopers]

Try to execute the same workflow with the following options to verify if the problem is raised from the executable itself.

Using the code compiled locally in generateclasses.yaml, the issue is not raised: see https://github.com/masesgroup/KNet/actions/runs/12443964377

[masesdevelopers]

generateclasses.yaml fails even if the latest package is fully compiled with CETCompat to false; there two possibility:

1. the package installed is the one published and not the one retrieved from last build of JNet
2. in any case, the command issued, since it use the assembly (), is executed from an executable that is not CET compatible

The workflow shall be updated in order to:

1. use exclusively the package from last JNet build
2. then shall be tested the direct command, not the shortcut.

[masesdevelopers]

generateclasses.yaml fails even if the latest package is fully compiled with CETCompat to false; there two possibility:

1. the package installed is the one published and not the one retrieved from last build of JNet

2. in any case, the command issued, since it use the assembly (), is executed from an executable that is not CET compatible

The workflow shall be updated in order to:

1. use exclusively the package from last JNet build

2. then shall be tested the direct command, not the shortcut.

Option 2 is not feasible, however it is possible to try the solution on https://edge.eastasia.cloudapp.azure.com/recipe/content/disable-user-mode-shadow-stack-cet-for-edge on dotnet or mases.jnetreflector.exe

[masesdevelopers]

generateclasses.yaml fails even if the latest package is fully compiled with CETCompat to false; there two possibility:

1. the package installed is the one published and not the one retrieved from last build of JNet

2. in any case, the command issued, since it use the assembly (), is executed from an executable that is not CET compatible

The workflow shall be updated in order to:

1. use exclusively the package from last JNet build

2. then shall be tested the direct command, not the shortcut.

Option 2 is not feasible, however it is possible to try the solution on https://edge.eastasia.cloudapp.azure.com/recipe/content/disable-user-mode-shadow-stack-cet-for-edge on dotnet or mases.jnetreflector.exe

The final solution, since the installation of tools creates an executable following what is written here, is to apply

reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\jnetreflector.exe" /v MitigationOptions /t REG_BINARY /d "0000000000000000000000000000002000" /f

in a shell under elevated privileges, like it is done in df22e5d.