File versioning 4.5.3, grrr!!!

System

OK, I have a huge issue with 4.5.3 file versioning. Why are the files versioned backwards to 4.5.0.24?

Why in the heck are the new version dll files 4.5.0.24 instead of 4.5.3.24? This causes me great grief from a support standpoint.

In many of my applications, we have an automatic updating tool, like Windows Update concept. Except, those files check version number on a file share and file on a client machine. If the file number is smaller than the new one, my tool automatically brings down and registers the new file.

Now, I can't do that and I am not happy.

Additionally to set me off even further, why is mbpscriptmodel2.dll 4.5.0.23 and not build 24? Arrghh!

To really set me over the edge, why is the Windows client About box say 4.5.3 build 16?

In the future, please put into your build, qa, and test cycles to check the versions of your DLLs before release. You'll make me very happy if you do that.

Sincerely,
Disgruntle in Seattle.