Update across filenames

My current project has a number of files named in this format: ProjectID_shortname_vXX. ProjectID and shortname are constant, but vXX increments with each version. Is there any way to update these files while still offering small, diffed updates?

wyBuild doesn't scan files with different filenames to see if they are similar to other files with different filenames in old versions. If we did that it would significantly slow down the patch creation process. That's why wyBuild only creates "delta patches" for files that have the same filenames in the new version as in the old version.

All other files are added as full files.

Why are you changing the filename for versions? I'll assume you do it so you (or your users) will know what version a particular file is. But why not just change an internal property of the file? For example, if the files are *.dll files you can just change the version property of the dll and keep the filename the same. Or if the file is some internal creation of your company you can add a special field to read the "internal" version of the file.

Sadly, this is part of a legacy project that I don't have much control over. The files do not have a header; they are raw data.

Would it be possible for me to modify the updater to ignore the _VXX_ string on files of a certain extension? Can you suggest a good place to start looking through the code?

Can you suggest a good place to start looking through the code?

wyBuild is where the patch creation takes place, and wyBuild isn't open source.

Sadly, this is part of a legacy project that I don't have much control over. The files do not have a header; they are raw data.

Can you just stop renaming the files? I don't see a practical purpose for renaming the files on updates.

I cannot, but this isn't a huge deal. We don't update many files at once - and none of the files are very large - so it is not a huge loss if the client has to download updated files in their entirety.

EDIT:The files have the version name in them for 'clarity' - both internally, and for our users. I disagree with this, because it makes version control ugly, but I do not have the authority to change it.