malixg
commented
5 years ago As a follow up, I realized this error only occurs when Debugging, which I could see as a desired result in some situations: particularly when then "anti debug" protection is enabled. However, I do NOT have that protection enabled, and this is for an SDK so I do need debugging to work. I will play around with the other protections some more and see if I can make it work. I currently have the following enabled: "anti ildasm" "rename" "anti tamper" "resources" "ctrl flow"
I was previously using the original ConfuserEx, but could never get resource obfuscation to work, so when I saw your fork I decided to give it a shot. When I try to consume my newly confused assemblies in any of my projects I receive the following error at startup:
Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem in 'x.vshost.exe'.
Additional information: The runtime has encountered a fatal error. The address of the error was at 0xecef57a6, on thread 0x1628. The error code is 0x80131623. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.