|
#1
|
|||
|
|||
Your projects are referencing
$(DefaultPlatformToolset) which the Make VS action doesn't know about. Code:
<OutDir>..\..\bin\$(DefaultPlatformToolset)\$(Configuration)\</OutDir> What you can do is add a Set Macro step before the Make VS action to set DefaultPlatformToolset = v143 with 'Add to environment variables...' checked, and the Make VS action will do the replacement on the VS variable from the environment variable. If the executable is created in that path, the action will be able to detect the change for incrementing. |
#2
|
|||
|
|||
I will try to change the build script but will you support $(DefaultPlatformToolset) in a future release?
All our libraries are using this macro, because they are built with/for different compiler versions. TIA Martin |
#3
|
|||
|
|||
Supported in the latest download (VisBuildDotNET.dll 10.9.0.3).
|
#4
|
|||
|
|||
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; Yesterday at 08:16 AM. |
#5
|
|||
|
|||
Try the latest download (VisBuildDotNET.dll 10.9.0.4).
|
|
|