*.exe and *.dll files that use the PE executable format, but they aren't directly executed by the non-Windows OS: instead they'll have a loader program that starts the. NET Core on a non-Windows OS, the ".NET assembly" files are still
WHAT'S EQUIIVANT TO GET INFO ON MAC FOR WINDOWS FILES KEYGEN
Other operating systems use different executable image formats: Linux and most Unixes use ELF, and macOS uses the "Mach-O" format - neither of which use VERSIONINFO. Note that VERSIONINFO is a Microsoft/Win32-specific data structure. This format has the ability to store "resources" in a dedicated section of the file which can optionally contain a VERSIONINFO record structure (represented in-memory as VS_VERSIONINFO). Windows's *.exe files use the "PE" executable image format: - this format is also used by. Because ELF and Mach-O executables do not contain a Win32 resources section you cannot use FileVersionInfo.GetVersionInfo() on those kinds of executables. NET assemblies specifically can be read, and not non-.NET assembly PE executables) can be read. This means that on Mac or Linux you can use FileVersionInfo.GetVersionInfo() to read only PE executable files, with the additional caveat that ( as of April 2021) only. NET assemblies always use the PE format, however, which means they can contain a VERSIONINFO structure in their resources section. On macOS and Linux, most (but not all) executables are Mach-O and ELF images respectively, which do not contain a VERSIONINFO structure at all.On Windows, most executables are PE images which may or may not contain a VERSIONINFO structure.The FileVersionInfo.GetVersionInfo() method attempts to read VERSIONINFO resource data from a Win32 PE binary executable image.
(Reposting my comment as an answer): Shortest answer:
0 kommentar(er)
