Make VS 2022 VERSIONINFO is not incremented

[kinook]

We did find an issue with the default target filename for x64 configuration not including the \x64 path in the filename, which would prevent the action from detecting a difference to increment the version. This is fixed in the latest download (VisBuildDotNET.dll 10.9.0.2).

If that doesn't resolve the issue, please provide the information requested at

https://www.kinook.com/Forum/showthread.php?t=3044

Thanks.

[mgampi]

Hello;
I just updated VBP to the latest release but the problem still exists.
We will provide the information as requested by the end of the day.

[mgampi]

Hi;

We found out, that the increment is only done, when we choose 'All' in 'Which solution or project config should be build or updated? ...'.
But in our case we are always generating only the Release|x64 configuration. As soon as we explicitely set this configuration, the increment stops working.
Why?

TIA

Martin

[kinook]

That was happening in our tests (attached) as well before the fix (when building all configurations, it correctly identified the x86 executable target filenames but not the x64). Please post the project files.

[mgampi]

Hello;

Which files do you need in detail?
Only the .vcxproj files or the .sln?
In addition, do you need the VBP build file too?

TIA

Martin

[kinook]

The .bld file, the .vxcproj file, the .sln (if that is what you're building), and the .rc files in the project.

[mgampi]

Find enclosed the requested files.
Currently we build only the Release|x64 configurations.