In general, I appeal to those who are good friends with encryption and obfuscation.

When compiling a program in MCVS2010 \ 2013, and indeed anywhere else, such nonsense creeps out, if the build is opened with a notebook:

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel> </requestedPrivileges> </security> </trustInfo> </assembly>

As well as a list of used libraries and a lot of other rubbish.

In general, how can you cut this rubbish from the finished build without affecting the program?

  • 2
    Remove hard from the computer and smash with a hammer. One of the most reliable methods (after burning in a thermonuclear furnace). - KoVadim
  • It is interesting how the author is going to obfuscate the used libraries, if in the absence of their application the applications fail with the message, I cannot find the library and then the full info, what exactly is missing, i.e. you can always understand exactly what is used. Actually, you can understand for sure without a launch, just in Windows I don’t know how (in nicks with ldd). - aknew
  • just in case @aknew - in Windows there is Dependency Walker, depends.exe - gbg

2 answers 2

Compile all libraries statically, including system libraries, remove all dynamic dependencies. Please note that your program will not be portable and will most likely work only on the system on which it was compiled.

  • @VladD, let me explain in more detail? 1. This is not a program as such, but a plugin. 2. Since There is no adequate way to compile plugins for this; everything compiles into VS10, using some third-party libraries. - Vitali RS

What is your goal? What exactly this XML didn’t please you? Read here: http://www.samlogic.net/articles/manifest.htm