Phil,

Based you the information below, it seems that you are using the appropriate 
version of MSBuild. Now, can you confirm that you C++ project is compiled using 
the same version of .net Framework?

i.e. do you have project in your solution which are compiled using different 
version of .net Framework?

-Anand


-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of 
seffyroff
Sent: Thursday, September 11, 2008 4:22 PM
To: ccnet-user
Subject: [ccnet-user] Re: MSBuild Include Paths Frustrations


Hi Anand,

Thanks for your reply.

You might be onto something there - when I run

C:\SVNProject\Project\Source>c:\windows\Microsoft.NET\Framework
\v3.5\MSBuild.exe /?

I get:

Microsoft (R) Build Engine Version 3.5.30729.1 [Microsoft .NET Framework, 
Version 2.0.50727.3053] Copyright (C) Microsoft Corporation 2007. All rights 
reserved.

I tried running it with /toolsversion:3.5 and it returned the same thing.  I 
have .net Framework 3.5SP1 installed.  What am I missing?


Phil.

On Sep 11, 11:39 am, "Desai, Anand" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> Are you sure that you are using .Net Framework 3.5 for this?
>
> Can you send the command line output when you try to run this command?
>
> -Anand
>
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] 
> On Behalf Of seffyroff
> Sent: Thursday, September 11, 2008 3:54 PM
> To: ccnet-user
> Subject: [ccnet-user] Re: MSBuild Include Paths Frustrations
>
> I'm calling msbuild.exe from the Windows\Microsoft.NET\Framework\v3.5\
> directory, and still getting these errors, so either I have something 
> set up wrong or MS didn't Iron out all the C++ kinks :(
>
> I can't seem to find anything relevant on the net related to this issue, 
> which makes it all the more frustrating, as I feel I must be doing something 
> wrong that everyone else got right!
>
> Anyone successfully managed to get a C++ .sln with multiple projects in it to 
> successfully build with CCNet?  Alex, you seem to suggest you have done so - 
> I'm not doing any multicore flag stuff, just a debug build targeted for 
> Windows DirectX.
>
> Here's my specific commandline:
>
> C:\SVNProject\Project\Source>c:\windows\Microsoft.NET\Framework
> \v3.5\MSBuild.exe Project.sln /p:Configuration=Debug / 
> p:Platform=DirectX /v:diag
>
> I've tried adding various things like "/p:"VCBuildAdditionalOptions=/ useenv" 
> and "/p:ReferencePath=pathtoincludedheaders" etc but none of those things 
> appeared to make any difference.
>
> Best regards,
>
> Phil
>
> On Sep 11, 2:27 am, Alex <[EMAIL PROTECTED]> wrote:
> > I never really found a working solution for this and ended up giving 
> > up on MsBuild 2.0.5727 with C++ projects. However if you can use 
> > MsBuild 3.5 you will find Microsoft ironed out all the C++ kinks. 
> > The only exception I have found is you can not build 64 bit targets 
> > with the multicore flag.
>
> > On Sep 10, 11:44 am, seffyroff <[EMAIL PROTECTED]> wrote:
>
> > > Hi again guys,
>
> > > I'm attempting to build a C++ project from a .sln which has 
> > > multiple projects in it, using MSBuild.  when I try and run 
> > > MSBuild from teh commandline with my sln file, Configuration and 
> > > Platform settings, it errors out because it can't find things like 
> > > cstdio, d3d9, windows.h etc.
>
> > > I've Googled and Googled and Googled and can't seem to find a way 
> > > to give MSBuild Include paths on the commandline.  Anybody 
> > > experienced this?  Am I approaching this wrong somewhow?
>
> ======================================================================
> ======== Please access the attached hyperlink for an important 
> electronic communications disclaimer:
>
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
> ======================================================================
> ========


==============================================================================
Please access the attached hyperlink for an important electronic communications 
disclaimer: 

http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================

Reply via email to