What could be the reason between a binary file in a package being different from the file that is published to the Bin folder?
I had done a MD5 hash comparison and the file in the Bin folder (after publishing) differs from the file in the Package. The only fix was to download the file from the Custom Package Files grid and copy it to the Bin folder.
Has anyone experienced this before? What could cause it?
Best answer by Desmond78
Expected behaviour was different on the dev instance to the test instance after publishing a dev package to the test instance.
DLL versions reported to be the same, but MD5 hashes were not the same.
Have recompiled against refreshed dependencies and the issue seems to be resolved. Thanks.
+1
+7There is a mechanism that patches the customization code while publishing.
E.g. if a customization code was for older Acumatica version initially and then published on a newer Acumatica version. In case some method signatures were changed, but the change is not significant and can be automatically patched in the DLL, the customization engine will do it in order to have less issues with binary compatibility of customizations.
Expected behaviour was different on the dev instance to the test instance after publishing a dev package to the test instance.
DLL versions reported to be the same, but MD5 hashes were not the same.
Have recompiled against refreshed dependencies and the issue seems to be resolved. Thanks.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
