|
#1
|
|||
|
|||
Supported in the latest download (VisBuildDotNET.dll 10.9.0.3).
|
#2
|
|||
|
|||
Hi;
Sorry for the delayed reply. I tried both - new DLL and the macro workaround - but both of them do not work! What I found out so far is: When compiling any of the 32-bit configuration ithe version number is increased, but as soon as we create a 64-bit configuration, the increment is not performed. As I mentioned before, we exclusively build only 64-bit configurations. Last edited by mgampi; 05-29-2024 at 08:16 AM. |
#3
|
|||
|
|||
Try the latest download (VisBuildDotNET.dll 10.9.0.4).
|
#4
|
|||
|
|||
Hello;
I tested with the release 10.9.0.4 but its still the same. 64-bit configurations are not incrementing the last number of the file version as shown in my previous post. |
#5
|
|||
|
|||
It worked in the test harness I created (attached).
Please provide a buildable project (and all source code files) that demonstrates the issue. Thanks. |
#6
|
|||
|
|||
Hello;
Find attached the updated .zip file with all source code files and the .bld file that demonstrates the issue. The Project1.bld file was used to generate the output shown in the screenshots above. Just extract the .zip and open the Project1.bld file and rebuild it. Then afterwards change the "Make VS 2022" build step to build just a x64 build configuration and once to just a x86 build configuration. Let me know if you can reproduce my results. TIA M |
#7
|
|||
|
|||
Fixed in the latest download (VisBuildDotNET.dll 10.9.0.5).
|
|
|