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 03-27-2006, 02:55 PM
mweinberger mweinberger is online now
Registered User
 
Join Date: 12-23-2005
Posts: 40
Controlling which version of Visual Studio VBPro Uses

Hi All,

My build machine has both VS2003 and VS2005 installed. I'm trying to build a C++ based solution using VBPro, but the product tries to use VS2003 to build and not VS2005 as it should.

I set one of the macro variables to VS2005 as you can see below, but that didn't do anything for my current problem. Which other variable/macro should I touch and to what?

Thanks in advance,

Martin

<macro name='DEVENV_NET'>
<description>Microsoft Visual Studio .NET command-line build tool</description>
<value>"%DEVSTUDIO_NET_DIR%\Common7\IDE\devenv.com "</value>
</macro>
<macro name='DEVSTUDIO_NET_DIR'>
<description>Microsoft Visual Studio .NET installation path</description>
<value>%MSVSTUDIO_2005%</value>
</macro>

<macro name='MSVSTUDIO_2003'>
<description>Microsoft Visual Studio 2003 root folder</description>
<value>C:\Program Files\Microsoft Visual Studio .NET 2003</value>
</macro>
<macro name='MSVSTUDIO_2005'>
<description>Microsoft Visual Studio 2005 root folder</description>
<value>C:\Program Files\Microsoft Visual Studio 8</value>
</macro>
Reply With Quote
  #2  
Old 03-27-2006, 03:16 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,034
The Make VS.NET action parses the solution/project file to determine the correct version of devenv/msbuild/vcbuild to invoke. You can override this via the 'Override...' field on the Options tab:
http://www.visualbuild.com/Manual/vsnetoptionstab.htm

But please ZIP and post or send:
1) The info from Help | About | Install Info
2) The .bld file used to build
3) A build log file
4) The .sln file and project files being built (no source code files)

as that shouldn't be necessary.
Reply With Quote
  #3  
Old 03-27-2006, 03:37 PM
mweinberger mweinberger is online now
Registered User
 
Join Date: 12-23-2005
Posts: 40
Here's the zip file

Evidently, the Make VS.Net step didn't parse the solution file correctly to determine the version number.
Attached Files
File Type: zip from_mweinberger.zip (13.9 KB, 1818 views)
Reply With Quote
  #4  
Old 03-27-2006, 03:49 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,034
In the .bld file you posted, the failing step named 'Build - vzDLUpgrade.sln - Debug Compile' is configured to use %7.1_compiler% (which expands to 'C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.com') in the previously mentioned Override field, which will override the default parsing of the .sln file for the version information. After I cleared out that field, it built the solution using MSBuild as expected (running on a box w/ VS2003 & 2005 installed).
Reply With Quote
  #5  
Old 03-27-2006, 05:09 PM
mweinberger mweinberger is online now
Registered User
 
Join Date: 12-23-2005
Posts: 40
Awesome Response!

Thank you!!!!!!

I didn't even see that line there. I'm not even sure why the build engineer before added that line. Thanks for pointing that out. Everything builds nicely, except for the get history error, which you or someone else said to contact Microsoft on. :'(

Thanks again,

Martin
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 07:35 AM.


Copyright © 1999-2023 Kinook Software, Inc.