Error building CPPCustomVisualizer example in VS 2019 16.3.8

[KorkyPlunger]

When I download the CPPCustomVisualizer example source code and, in VS 2019 16.3.8, right-click on the 'vsix' project and build in release, there is an error at the end of the build process and the build fails with the following error:

2>VSSDK : error VSSDK1025: Could not add the file 'C:\Users\ckline\dev\c\CppCustomVisualizer\Release\x86\CppCustomVisualizer.vsdconfig' to the zip package 'C:\Users\ckline\dev\c\CppCustomVisualizer\Release\CppCustomVisualizer.vsix'. Could not find a part of the path 'C:\Users\ckline\dev\c\CppCustomVisualizer\Release\x86\CppCustomVisualizer.vsdconfig'.

Here's the build output:

1>------ Build started: Project: CppCustomVisualizer, Configuration: Release x64 ------
1>stdafx.cpp
1>dllmain.cpp
1>_EntryPoint.cpp
1>Generating Code...
1>   Creating library C:\Users\ckline\dev\c\CppCustomVisualizer\Release\x64\CppCustomVisualizer.lib and object C:\Users\ckline\dev\c\CppCustomVisualizer\Release\x64\CppCustomVisualizer.exp
1>CppCustomVisualizer.vcxproj -> C:\Users\ckline\dev\c\CppCustomVisualizer\Release\x64\CppCustomVisualizer.dll
2>------ Build started: Project: vsix, Configuration: Release Win32 ------
2>Build started 11/7/2019 9:55:23 AM.
2>     1>Project "C:\Users\ckline\dev\c\CppCustomVisualizer\CppCustomVisualizer.sln" on node 1 (Build target(s)).
2>     1>ValidateSolutionConfiguration:
2>         Building solution configuration "Release|x64".
2>       ValidateProjects:
2>         The project "vsix" is not selected for building in solution configuration "Release|x64".
2>     1>Project "C:\Users\ckline\dev\c\CppCustomVisualizer\CppCustomVisualizer.sln" (1) is building "C:\Users\ckline\dev\c\CppCustomVisualizer\dll\CppCustomVisualizer.vcxproj" (2) on node 1 (default targets).
2>     2>InitializeBuildStatus:
2>         Creating "Release\x64\CppCusto.F7062FB7.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
2>       CreateVsdbgConfigContract:
2>       Skipping target "CreateVsdbgConfigContract" because all output files are up-to-date with respect to the input files.
2>       ClCompile:
2>         All outputs are up-to-date.
2>         All outputs are up-to-date.
2>       ResourceCompile:
2>         All outputs are up-to-date.
2>       Link:
2>         All outputs are up-to-date.
2>         CppCustomVisualizer.vcxproj -> C:\Users\ckline\dev\c\CppCustomVisualizer\Release\x64\CppCustomVisualizer.dll
2>       CreateVsdbgConfigFile:
2>       Skipping target "CreateVsdbgConfigFile" because all output files are up-to-date with respect to the input files.
2>       FinalizeBuildStatus:
2>         Deleting file "Release\x64\CppCusto.F7062FB7.tlog\unsuccessfulbuild".
2>         Touching "Release\x64\CppCusto.F7062FB7.tlog\CppCustomVisualizer.lastbuildstate".
2>     2>Done Building Project "C:\Users\ckline\dev\c\CppCustomVisualizer\dll\CppCustomVisualizer.vcxproj" (default targets).
2>     1>Done Building Project "C:\Users\ckline\dev\c\CppCustomVisualizer\CppCustomVisualizer.sln" (Build target(s)).
2>
2>Build succeeded.
2>    0 Warning(s)
2>    0 Error(s)
2>
2>Time Elapsed 00:00:00.48

2>VSSDK : error VSSDK1025: Could not add the file 'C:\Users\ckline\dev\c\CppCustomVisualizer\Release\x86\CppCustomVisualizer.vsdconfig' to the zip package 'C:\Users\ckline\dev\c\CppCustomVisualizer\Release\CppCustomVisualizer.vsix'. Could not find a part of the path 'C:\Users\ckline\dev\c\CppCustomVisualizer\Release\x86\CppCustomVisualizer.vsdconfig'.

2>Done building project "vsix.vcxproj" -- FAILED.

========== Build: 1 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

[gregg-miskelly]

I believe this is because your active processor is set to 'x64'. Change it to 'x86'. I will see if I can figure out why the solution defaults to 'x64'.

[gregg-miskelly]

There doesn't seem to be a way to control the order - it will pick 'x64' because it is alphabetically first. But I did tweak the instructions to try and make it more clear that you need to switch to x86.

[KorkyPlunger]

Thank you, @gregg-miskelly. That was indeed the issue for me. Not sure why I didn't try x86.