FileVersionInfo.GetVersionInfo alternative

Question

I have an application that checks for updates. To check for updates I need to get the version of the file on the user's computer. I used this code:

if (File.Exists(dataFile))
{
    var verLocal = Version.Parse(FileVersionInfo.GetVersionInfo(dataFile).FileVersion);
    if (verSite > verLocal)
    {
        needToAdd = true;
    }
}

Today I found out that the method FileVersionInfo.GetVersionInfo(String) may not get the file version! Here is a description from the help:

If the file did not contain version information, the FileVersionInfo contains only the name of the file requested.

So that there was no error, I did like this:

if (File.Exists(dataFile))
{
    if (Version.TryParse(FileVersionInfo.GetVersionInfo(dataFile).FileVersion, out var verLocal))
    {
        if (verSite > verLocal)
        {
            needToAdd = true;
        }
    }
}

But now there is a problem - if the user this method will never return the version of the file, then the user will never receive updates! So I need a way to get the version of the file that always works.

Are there alternatives to this method in c#?

Answer 1

That Version info metadata really only applies the Executeables or DLL's. It is supposed to be set during compilation. I have not seen it apply (be written) to any word document, image or similar non-executeable file.

A pretty dated approach for archiving, would be the old Archive Bit/Atribute. Just throwing it out there for completeness.

Usually for a "did it change?" check, it is sufficient to just check the file Size and LastUpdated dates of the file for changes. If you pick any backup maker, it will not do more advanced checks then this (plus the archive bit thing as a option). That one of those two values does not change can happen. But both of them is to unlikely to bother with.

The only 100%* reliable way to check for changes is to calculate a files hash-value. But that usually is something you only do during stuff like install verifications, not as a basic backup.

*Technically not even that is 100%. Hash Colissions are a thing, but are realistically impossible if you already check size and change date.