Version not updated with 7.0.7 SR1a upgrade

[mfreeze]

I have upgraded a couple of my 7.0.7 sites to SR1a and noticed that the version number is not updating. When I check About after the upgrade I still see the following.

AbleCommerce for ASP.NET
AbleCommerce for ASP.NET
VERSION: 7.0.7.14481
MSSQL v2005
AC SCHEMA v2000
.NET CLR v2.0.50727.3620
ASP.NET TRUST: Unrestricted

[jmestep]

Did you upload the VersionInfo.xml in the App_Data folder of SR1?
I missed that one myself when I applied SR1.

[mfreeze]

Yes. That file says <BuildNumber>14481</BuildNumber> but the doc says it should be 7.0.7 SR1a (build 14600).

I manually changed that line on the site I just updated

[Logan Rhodehamel]

There is an updated App_Data/VersionInfo.xml file distributed with the patch and with the upgrade build. This file must be deployed along with the patch/upgrade to get the updated version listed. It's not automatic like the versioning for the DLL assemblies.

[jmestep]

That's weird. Maybe something got reverted back in a package. My file in SR1 says build number 14588 not 14600. But when I downloaded it on 6/23 it was SR1 and now it is SR1a and it still says 14588 in the xml file, but I do see in the readme for SR1a it says Build 14600.

[jmestep]

I just did an upgrade to 707 on a site today and was making sure they had the latest patches and ran across some weird versioning. Here is a BeyondCompare report and it shows that some of the files in SR1a(which I downloaded this morning) are older than in SR1. SR1a is on the right, SR1 is on the left.
What should we do- which should we use?

707SR1vsSR1a.png

[Logan Rhodehamel]

The files from the SR1a patch are the best ones to use. From your comparison it appears as though two files went down in version. Actually what happened is we included "new" versions of these files in the original SR1 file, but these files were not any different except in version number. We reverted the files back to the versions released with the original 7.0.7 to keep things simple and avoid updating files without any reason. Since you already applied the patch, it appears to go down in version, but for people newly applying the patch it will just seem to be an unmodified file.