C# FileVersionInfo.GetVersionInfo (FilePath) behaves strangely
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I am trying to read the file version from an exe file. ( - not product version.)
I tested two sample codes.
var versionInfo = FileVersionInfo.GetVersionInfo(FilePath);
string Description = versionInfo .FileDescription;
string Company = versionInfo.CompanyName;
//1
string Fileversion1 = string.Format("0.1.2.3", versionInfo.FileMajorPart, versionInfo.FileMinorPart, versionInfo.FileBuildPart, versionInfo.FilePrivatePart);
//2
string Fileversion2 = versionInfo.FileVersion;
The result is shown below.
The following figure is an actual property of PowerShell.
MS applications such as notepad, cmd will get the same results as POwershell.
Check Putty with the same code:
I would like to know the file version in the properties of the application.
I have a history of upgrading from Windows8 to Windows10 through a free upgrade to Windows10.
Can this behavior affect the outcome?
c# windows-10 fileversioninfo
asked Nov 15 '18 at 7:26
cskangcskang
385
add a comment |
I am trying to read the file version from an exe file. ( - not product version.)
I tested two sample codes.
var versionInfo = FileVersionInfo.GetVersionInfo(FilePath);
string Description = versionInfo .FileDescription;
string Company = versionInfo.CompanyName;
//1
string Fileversion1 = string.Format("0.1.2.3", versionInfo.FileMajorPart, versionInfo.FileMinorPart, versionInfo.FileBuildPart, versionInfo.FilePrivatePart);
//2
string Fileversion2 = versionInfo.FileVersion;
The result is shown below.
The following figure is an actual property of PowerShell.
MS applications such as notepad, cmd will get the same results as POwershell.
Check Putty with the same code:
I would like to know the file version in the properties of the application.
I have a history of upgrading from Windows8 to Windows10 through a free upgrade to Windows10.
Can this behavior affect the outcome?
c# windows-10 fileversioninfo
asked Nov 15 '18 at 7:26
cskangcskang
385
What are differences between AssemblyVersion, AssemblyFileVersion and AssemblyInformationalVersion?
– Jimi
Nov 15 '18 at 8:37
I cannot reproduce this on my Win10 installation.FileVersionInfo.GetVersionInfo(@"C:WindowsSystem32WindowsPowerShellv1.0powershell.exe")gives10for theFileMajorPart. Check if your application has some app compat setting applied to it -- if possible, rebuild it somewhere else, rename it, and make sure there are no compatibility settings applied.
– Jeroen Mostert
Nov 15 '18 at 8:46
@Jeroen Mostert The OP probably has the April 2018 PowerShell update. That will return a Major version as reported.
– Jimi
Nov 15 '18 at 9:21
1
This is normal for Win10. It used to be that the appcompat team at Microsoft had to test tens of thousands of commonly used programs, creating an appcompat shim if the program refused to run on a higher version number. They gave up on that for Win10, it stopped being practical. It won't lie about the version number if your program was built to target Win10. Awkward to do in C#, you have to run Editbin.exe to patch the file header, /subsystem option. But your program will now only run on Win10.
– Hans Passant
Nov 15 '18 at 10:19
add a comment |
I am trying to read the file version from an exe file. ( - not product version.)
I tested two sample codes.
var versionInfo = FileVersionInfo.GetVersionInfo(FilePath);
string Description = versionInfo .FileDescription;
string Company = versionInfo.CompanyName;
//1
string Fileversion1 = string.Format("0.1.2.3", versionInfo.FileMajorPart, versionInfo.FileMinorPart, versionInfo.FileBuildPart, versionInfo.FilePrivatePart);
//2
string Fileversion2 = versionInfo.FileVersion;
The result is shown below.
The following figure is an actual property of PowerShell.
MS applications such as notepad, cmd will get the same results as POwershell.
Check Putty with the same code:
I would like to know the file version in the properties of the application.
I have a history of upgrading from Windows8 to Windows10 through a free upgrade to Windows10.
Can this behavior affect the outcome?
c# windows-10 fileversioninfo
asked Nov 15 '18 at 7:26
cskangcskang
385
I am trying to read the file version from an exe file. ( - not product version.)
I tested two sample codes.
var versionInfo = FileVersionInfo.GetVersionInfo(FilePath);
string Description = versionInfo .FileDescription;
string Company = versionInfo.CompanyName;
//1
string Fileversion1 = string.Format("0.1.2.3", versionInfo.FileMajorPart, versionInfo.FileMinorPart, versionInfo.FileBuildPart, versionInfo.FilePrivatePart);
//2
string Fileversion2 = versionInfo.FileVersion;
The result is shown below.
The following figure is an actual property of PowerShell.
MS applications such as notepad, cmd will get the same results as POwershell.
Check Putty with the same code:
I would like to know the file version in the properties of the application.
I have a history of upgrading from Windows8 to Windows10 through a free upgrade to Windows10.
Can this behavior affect the outcome?
c# windows-10 fileversioninfo
c# windows-10 fileversioninfo
asked Nov 15 '18 at 7:26
cskangcskang
385
asked Nov 15 '18 at 7:26
cskangcskang
385
asked Nov 15 '18 at 7:26
cskangcskang
385
asked Nov 15 '18 at 7:26
cskangcskang
385
asked Nov 15 '18 at 7:26
cskangcskang
385
385
What are differences between AssemblyVersion, AssemblyFileVersion and AssemblyInformationalVersion?
– Jimi
Nov 15 '18 at 8:37
I cannot reproduce this on my Win10 installation.FileVersionInfo.GetVersionInfo(@"C:WindowsSystem32WindowsPowerShellv1.0powershell.exe")gives10for theFileMajorPart. Check if your application has some app compat setting applied to it -- if possible, rebuild it somewhere else, rename it, and make sure there are no compatibility settings applied.
– Jeroen Mostert
Nov 15 '18 at 8:46
@Jeroen Mostert The OP probably has the April 2018 PowerShell update. That will return a Major version as reported.
– Jimi
Nov 15 '18 at 9:21
1
This is normal for Win10. It used to be that the appcompat team at Microsoft had to test tens of thousands of commonly used programs, creating an appcompat shim if the program refused to run on a higher version number. They gave up on that for Win10, it stopped being practical. It won't lie about the version number if your program was built to target Win10. Awkward to do in C#, you have to run Editbin.exe to patch the file header, /subsystem option. But your program will now only run on Win10.
– Hans Passant
Nov 15 '18 at 10:19
add a comment |
What are differences between AssemblyVersion, AssemblyFileVersion and AssemblyInformationalVersion?
– Jimi
Nov 15 '18 at 8:37
I cannot reproduce this on my Win10 installation.FileVersionInfo.GetVersionInfo(@"C:WindowsSystem32WindowsPowerShellv1.0powershell.exe")gives10for theFileMajorPart. Check if your application has some app compat setting applied to it -- if possible, rebuild it somewhere else, rename it, and make sure there are no compatibility settings applied.
– Jeroen Mostert
Nov 15 '18 at 8:46
@Jeroen Mostert The OP probably has the April 2018 PowerShell update. That will return a Major version as reported.
– Jimi
Nov 15 '18 at 9:21
1
This is normal for Win10. It used to be that the appcompat team at Microsoft had to test tens of thousands of commonly used programs, creating an appcompat shim if the program refused to run on a higher version number. They gave up on that for Win10, it stopped being practical. It won't lie about the version number if your program was built to target Win10. Awkward to do in C#, you have to run Editbin.exe to patch the file header, /subsystem option. But your program will now only run on Win10.
– Hans Passant
Nov 15 '18 at 10:19
What are differences between AssemblyVersion, AssemblyFileVersion and AssemblyInformationalVersion?
– Jimi
Nov 15 '18 at 8:37
What are differences between AssemblyVersion, AssemblyFileVersion and AssemblyInformationalVersion?
– Jimi
Nov 15 '18 at 8:37
I cannot reproduce this on my Win10 installation.
FileVersionInfo.GetVersionInfo(@"C:WindowsSystem32WindowsPowerShellv1.0powershell.exe") gives 10 for the FileMajorPart. Check if your application has some app compat setting applied to it -- if possible, rebuild it somewhere else, rename it, and make sure there are no compatibility settings applied.– Jeroen Mostert
Nov 15 '18 at 8:46
I cannot reproduce this on my Win10 installation.
FileVersionInfo.GetVersionInfo(@"C:WindowsSystem32WindowsPowerShellv1.0powershell.exe") gives 10 for the FileMajorPart. Check if your application has some app compat setting applied to it -- if possible, rebuild it somewhere else, rename it, and make sure there are no compatibility settings applied.– Jeroen Mostert
Nov 15 '18 at 8:46
@Jeroen Mostert The OP probably has the April 2018 PowerShell update. That will return a Major version as reported.
– Jimi
Nov 15 '18 at 9:21
@Jeroen Mostert The OP probably has the April 2018 PowerShell update. That will return a Major version as reported.
– Jimi
Nov 15 '18 at 9:21
1
1
This is normal for Win10. It used to be that the appcompat team at Microsoft had to test tens of thousands of commonly used programs, creating an appcompat shim if the program refused to run on a higher version number. They gave up on that for Win10, it stopped being practical. It won't lie about the version number if your program was built to target Win10. Awkward to do in C#, you have to run Editbin.exe to patch the file header, /subsystem option. But your program will now only run on Win10.
– Hans Passant
Nov 15 '18 at 10:19
This is normal for Win10. It used to be that the appcompat team at Microsoft had to test tens of thousands of commonly used programs, creating an appcompat shim if the program refused to run on a higher version number. They gave up on that for Win10, it stopped being practical. It won't lie about the version number if your program was built to target Win10. Awkward to do in C#, you have to run Editbin.exe to patch the file header, /subsystem option. But your program will now only run on Win10.
– Hans Passant
Nov 15 '18 at 10:19
add a comment |
1 Answer
1
active
oldest
votes
The documentation of property FileVersion is misleading. It makes you think it is a concatenation of major, minor, build and private numbers.
Actually, FileVersion is extracted using a call to a system API function (VerQueryValue), which can returns something different.
answered Nov 15 '18 at 8:44
NickNick
2,3471215
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53314341%2fc-sharp-fileversioninfo-getversioninfo-filepath-behaves-strangely%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The documentation of property FileVersion is misleading. It makes you think it is a concatenation of major, minor, build and private numbers.
Actually, FileVersion is extracted using a call to a system API function (VerQueryValue), which can returns something different.
answered Nov 15 '18 at 8:44
NickNick
2,3471215
add a comment |
The documentation of property FileVersion is misleading. It makes you think it is a concatenation of major, minor, build and private numbers.
Actually, FileVersion is extracted using a call to a system API function (VerQueryValue), which can returns something different.
answered Nov 15 '18 at 8:44
NickNick
2,3471215
add a comment |
The documentation of property FileVersion is misleading. It makes you think it is a concatenation of major, minor, build and private numbers.
Actually, FileVersion is extracted using a call to a system API function (VerQueryValue), which can returns something different.
answered Nov 15 '18 at 8:44
NickNick
2,3471215
The documentation of property FileVersion is misleading. It makes you think it is a concatenation of major, minor, build and private numbers.
Actually, FileVersion is extracted using a call to a system API function (VerQueryValue), which can returns something different.
answered Nov 15 '18 at 8:44
NickNick
2,3471215
answered Nov 15 '18 at 8:44
NickNick
2,3471215
answered Nov 15 '18 at 8:44
NickNick
2,3471215
answered Nov 15 '18 at 8:44
NickNick
2,3471215
2,3471215
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53314341%2fc-sharp-fileversioninfo-getversioninfo-filepath-behaves-strangely%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What are differences between AssemblyVersion, AssemblyFileVersion and AssemblyInformationalVersion?
– Jimi
Nov 15 '18 at 8:37
I cannot reproduce this on my Win10 installation.
FileVersionInfo.GetVersionInfo(@"C:WindowsSystem32WindowsPowerShellv1.0powershell.exe")gives10for theFileMajorPart. Check if your application has some app compat setting applied to it -- if possible, rebuild it somewhere else, rename it, and make sure there are no compatibility settings applied.– Jeroen Mostert
Nov 15 '18 at 8:46
@Jeroen Mostert The OP probably has the April 2018 PowerShell update. That will return a Major version as reported.
– Jimi
Nov 15 '18 at 9:21
1
This is normal for Win10. It used to be that the appcompat team at Microsoft had to test tens of thousands of commonly used programs, creating an appcompat shim if the program refused to run on a higher version number. They gave up on that for Win10, it stopped being practical. It won't lie about the version number if your program was built to target Win10. Awkward to do in C#, you have to run Editbin.exe to patch the file header, /subsystem option. But your program will now only run on Win10.
– Hans Passant
Nov 15 '18 at 10:19