File Versions are incorrect at 7.6.4+
-
Just realized while packaging 7.6.4, that the file version for notepad++.exe is now 7.64. Using a PowerShell script to detect the version as SCCM will not detect it using it’s internal detect method. Is this the versioning going forward? Or did someone just forget to add a decimal point?
-
Verified the same condition on 7.6.6 (shows as 7.66)
[version]$requiredVersion = ‘7.66’
$Path = “${ENV:ProgramFiles}\Notepad++”
Try {
[version]$installedVersion = (Get-Item -Path “$path\notepad++.exe” -ErrorAction “Stop”).VersionInfo.ProductVersion -as [version]
If ($installedVersion -eq $requiredVersion) {
Return 0
} else {
# remove for detection to work
$installedVersion
}
} Catch {}Major Minor Build Revision
===== ===== ==== =======
7 66 -1 -1 -
welcome to the notepad++ community, @KryptykHermit
this has almost always been like that (except faulty versioning versions 7.6.1 to 7.6.3)
file version will be 7.x.x.x
product version will be 7.xxthis product version scheme
M.mmis also what the auto updater and the notepad++ update servers expect.if you have written your script based on 7.6.1 to 7.6.3, you will have to modify them accordingly.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login