x64 broken?

[whbloodworth]

We're trying to use VisualBuild to build our product for both 64 and 32 bit platforms. They both build fine under DevStudio 2005 and use the project configuration settings correctly. However, when VisualBuild builds the solutions, the output destination folders seem to be ignored... and the projects are all building under the x86 configuration instead of the chosen x64 configuration.

I can get around this by creating entirely new configurations and naming them something like Debug 64 and Release 64. However, this makes the solution and project files confusing and messy.

Anyone run into this problem?

Thanks!

- William

[kinook]

VBP's Make VS.NET action invokes the VS command-line compiler (devenv.com) to actually build a project or solution. It sounds like VS does something different when invoked from the command-line vs. building in the IDE. Could you ZIP and post or send to support@kinook.com your solution+project files (no source code files), along with the info from Help | About | Install Info? Thanks.

[whbloodworth]

Sure,

Here is the information from the Help | Info window:

Visual Build Professional 6.0a
Registered to: Numerant LLC (ASP# 05903)
Windows Version: 5.1.2600.2.0
Install path: C:\Program Files\VisBuildPro6
SftTree_IX86_U_50.dll version 5.02
unins000.exe version 51.42.0.0
VisBuildCmd.exe version 6.0.1.1
VisBuildPro.exe version 6.0.1.3
VisBuildBld.dll version 6.0.1.2
VisBuildCore.dll version 6.0.1.2
VisBuildDotNET.dll version 6.0.1.2
VisBuildExt.dll version 6.0.1.2
VisBuildLog.dll version 6.0.1.1
VisBuildMisc.dll version 6.0.1.2
VisBuildMS.dll version 6.0.1.1
VisBuildMS2.dll version 6.0.1.0
VisBuildNet.dll version 6.0.1.1
VisBuildSvr.dll version 6.0.1.2
VisBuildSvr.Interop.dll version 1.0.0.0

And The other files are attached as requested. Of course, I've only included one of the solutions (and the two project files) that are in the VBP project (which is also included).

- William

[kinook]

My original statement wasn't quite true -- Make VS.NET can use MSBuild, devenv, or vcbuild to build a solution (and uses MSBuild by default). There's a bug in the Make VS.NET action that prevents multiple platforms for a configuration from building via MSBuild. For now, you can workaround it by building via devenv (enter devenv in the Override field on the Options tab). Also, just FYI, you can specify a regex wildcard (i.e., Debug.*) to build all platforms for a given configuration in one step.

[jannlin]

Do we have final answer about this thread? So we can use devenv to build 64 bit solution? Thanks.

[kinook]

There was never a VBP problem regarding building specific platform configurations for VS projects/solutions with devenv. This bug had to do with building a specific platform configuration with MSBuild. And it was fixed in VBP v6.1: http://www.kinook.com/Forum/showthre...?threadid=1596