Skip to main content
Reverse Engineering

Return to Answer

Download link to Detect it Easy changed
Source Link
edit approved Jan 12, 2018 at 16:25
Abhinav
edit approved Jan 12, 2018 at 16:25
Abhinav
  • 103
  • 3
  1. .NET could be identified by import which you can see using dependency warker - check if there is an import of mscorlib.dll which is a core lib of .net framework.
  2. C++ can be identified by
  3. looking at the assembly - it uses this call convention.
  4. PEid can show partial info about what compiler and run-time were used. In general it uses list of signature for that.
  5. Detect It EasyDetect It Easy - this tool is still maintained and has pretty interesting features.
  1. .NET could be identified by import which you can see using dependency warker - check if there is an import of mscorlib.dll which is a core lib of .net framework.
  2. C++ can be identified by
  3. looking at the assembly - it uses this call convention.
  4. PEid can show partial info about what compiler and run-time were used. In general it uses list of signature for that.
  5. Detect It Easy - this tool is still maintained and has pretty interesting features.
  1. .NET could be identified by import which you can see using dependency warker - check if there is an import of mscorlib.dll which is a core lib of .net framework.
  2. C++ can be identified by
  3. looking at the assembly - it uses this call convention.
  4. PEid can show partial info about what compiler and run-time were used. In general it uses list of signature for that.
  5. Detect It Easy - this tool is still maintained and has pretty interesting features.
added 171 characters in body
Source Link
PhoeniX
PhoeniX
  • 3.1k
  • 18
  • 30
  1. .NET could be identified by import which you can see using dependency warker - check if there is an import of mscorlib.dll which is a core lib of .net framework.
  2. C++ can be identified by
  3. looking at the assembly - it uses this call convention.
  4. PEid can show partial info about what compiler and run-time were used. In general it uses list of signature for that.
  5. Detect It Easy - this tool is still maintained and has pretty interesting features.
  1. .NET could be identified by import which you can see using dependency warker - check if there is an import of mscorlib.dll which is a core lib of .net framework.
  2. C++ can be identified by
  3. looking at the assembly - it uses this call convention.
  4. PEid can show partial info about what compiler and run-time were used. In general it uses list of signature for that.
  1. .NET could be identified by import which you can see using dependency warker - check if there is an import of mscorlib.dll which is a core lib of .net framework.
  2. C++ can be identified by
  3. looking at the assembly - it uses this call convention.
  4. PEid can show partial info about what compiler and run-time were used. In general it uses list of signature for that.
  5. Detect It Easy - this tool is still maintained and has pretty interesting features.
Source Link
PhoeniX
PhoeniX
  • 3.1k
  • 18
  • 30

  1. .NET could be identified by import which you can see using dependency warker - check if there is an import of mscorlib.dll which is a core lib of .net framework.
  2. C++ can be identified by
  3. looking at the assembly - it uses this call convention.
  4. PEid can show partial info about what compiler and run-time were used. In general it uses list of signature for that.