The use of obfuscator makes your application suspicious because you are intentionally hiding your source code. There is no other purpose for an obfuscator than to hide the construction of a binary on your target machine.
Furthermore, it is semantically impossible to fully protect your application against decompilation. Obfuscator only makes it harder, just like Trojans and Crypters. Here I explained what makes an app "potentially dangerous" and how you can get around it.
About in Debug it be recognized as a virus and in Release no, it is by the sessions where they are being called. In Visual Studio, when you debug a program, you start it on a server dedicated to VS debugging, however, an external binary performs the operations and forwards the addresses to the output executable.
After compiling in Debug, the generated symbols are also passed as Debug and have a structure where the vscode.exe
be monitoring (but not required). In short, the build architecture varies from the compiler parameters. This is also understood from anti-virus to anti-virus. Each has its own algorithm.
What kind of application is it (desktop, console, web)? Is this problem happening in the development, testing or production environment? This application is distributed to only one specific customer or multiple customers?
– user131248
Desktop, a simple application to generate ZPL labels for Zebra, on all company machines that use Bitdefender, even in which I develop the application.
– Marcos Barbosa
Yes, this is a fairly common problem in off-the-shelf software. Especially when overshadowed.
– user131248