Kinook Software Forum

Go Back   Kinook Software Forum > Visual Build Professional > [VBP] Third Party Tools
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 01-28-2008, 03:24 PM
ebriggs ebriggs is online now
Registered User
 
Join Date: 01-28-2008
Posts: 4
Question Make VS.NET bug in Visual Build?

We're currently using Visual Build Pro v5.7, and I'm having some trouble with the VS.NET step. We have the following configurations in our Visual Studio 2005 solution:

Debug|Any CPU
Debug|x86
Internal|Any CPU
Internal|x86
Release|Any CPU
Release|x86

I want to build the "Release|x86" configuration, so I've selected the "Release|x86" option from the Configuration(s) dropdown. The problem is that everytime I run this step, it builds the "Release|Any CPU" configuration instead.

This same problem occurs if I try to build the "Debug|x86" or "Internal|x86" configurations. It builds the corresponding "Any CPU" configuration instead.

Does anyone know if this is actually a bug in Visual Build (or am I just missing something...?)? If so, has it been fixed in the latest version? I looked through the release notes for each version after v5.7, but didn't see any bug fixes that definitely sounded like this problem.

Thanks!
Reply With Quote
  #2  
Old 01-28-2008, 03:28 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,034
VBP v6.0 was the first version to support Visual Studio 2005.
http://www.kinook.com/Forum/showthre...?threadid=1315
Reply With Quote
  #3  
Old 01-28-2008, 04:10 PM
ebriggs ebriggs is online now
Registered User
 
Join Date: 01-28-2008
Posts: 4
That would explain it; VS 2003 didn't allow multiple platforms per configuration. Thanks!
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 05:44 PM.


Copyright © 1999-2023 Kinook Software, Inc.