On 03/29/18 18:17, Robert via Boost wrote:
Note that the Visual Studio 2017 default for all new projects/solutions is 32-bit, x86 (aka Win32). In older Visual Studio releases, extra mouse clicks are required to configure a project to compile as x64. If there are a family of projects within an existing solution, then all projects individual project files will likely have to be manually edited to support x64. Ask me how I know.
Also note that until proven otherwise, the Boost Unit Test Adapter fork by Microsoft only integrates with Visual Studio 2017 correctly when set to x86 | Release. No other configuration setting will run within the IDE, let alone integrate correctly with the Visual Studio 2017 environment. When this is finally fixed, I have no idea. You will have to ask the Microsoft team managing the Boost Unit Test Adapter fork.
Difficulty with one particular IDE does not count as a valid reason to stick with 32-bit x86 to me.