When the comparer looks at the 2 DLL's it prints out the following message for almost all the DLLs.
Code: Select all
INFO Different content...
INFO File Key: Company_QBlender.dll is modified
INFO Comparing Files: C:\tmp\04\generationq-sp1\images\generation_1\DLL_Code_Release\Company_QBlenderPlugin3DCompositor.dll C:\tmp\04\generationq-sp1\images\generation_21\DLL_Code_Release\Company_QBlenderPlugin3DCompositor.dll...
INFO Comparing bytes...
----------------------\/
WARNING: File versions for target file: C:\tmp\04\generationq-sp1\images\generation_1\DLL_Code_Release\Company_QBlenderPlugin3DCompositor.dll and upgrade file: C:\tmp\04\generationq-sp1\images\generation_21\DLL_Code_Release\Company_QBlenderPlugin3DCompositor.dll are same, while the files itself are different.
----------------------/\
INFO Different content...
INFO File Key: Company_QBlenderPlugin3DCompositor.dll is modified
INFO Comparing Files: C:\tmp\04\generationq-sp1\images\generation_1\DLL_Code_Release\Company_QBlenderPluginBlur.dll C:\tmp\04\generationq-sp1\images\generation_21\DLL_Code_Release\Company_QBlenderPluginBlur.dll...
If this is the case how do I treat DLL's which are different on a binary level but the same on a DLL version number level as being equivalent? If the DLL version number has not changed then there is no need to update the binary even though it is different.
Is there a flag I can set somewhere or something?
FOLLOW US
Get the latest news in Application Packaging