Hi,
I have used VMProtect to protect a COM DLL,
on .NET 3.5, it is ok to add a COM reference and run it without popping up 'A debugger has been found .. unload it ... '
however, on .NET 4.0, i tried different COM properties without luck, it always disables the COM object calls.
any ideas? I don't want to generally disable the 'checking' of the debugger on VMProtect.
Thanks.
Is it possible to bypass .NET 4.0 checks on debugger
Is it possible to bypass .NET 4.0 checks on debugger
- Attachments
-
- Untitled.png (41.89 KiB) Viewed 14361 times