Instead of running MSBUILD on the solution file, have you tried to run
it on just the project file?
Or, you can still run it on the solution file, and target just one
specific project in the solution using the /t switch.

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
> Hi,
> I'm facing a problem while building a project through MSBuild, this
[quoted text clipped - 4 lines]
> Configuration Manager under solution properties, but how to achive
> same for a project!
ramshankaryadav@gmail.com - 06 Dec 2007 04:57 GMT
Hi Nicholas,
The problem is that we are migrating from .NET 1.1 to .NET 2.0, and we
used NAnt to build our solutions, using <solution> tag like this,
<solution configuration="${project.config}" failonerror="true"
outputdir="${output.dir}">
<projects>
<include name="myproject.csproj" /
..........
but because of change in the project structure of VS .NET 2005, which
is MSBuild compliant, our previous build file fails to build.
After some diagnosis, we found that we need to invoke MSBuild using
<exec> tag like this
<exec program="MSBuild" commandline="myproject.vcproj /
property:Configuration=${project.config};OutputPath=${path::get-full-
path(output.dir)}" verbose="false"/>
now the problem is ........
when I execute this script, it rebuilds it's dependent projects as
well, which I don't want to do!
I hope this explanation would be useful to you!
Thanks in advance!
Cheers,
Ram
On Dec 5, 9:32 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guard.caspershouse.com> wrote:
> Instead of runningMSBUILDon the solution file, have you tried to run
> it on just the project file?
[quoted text clipped - 20 lines]
>
> - Show quoted text -
Nicholas Paldino [.NET/C# MVP] - 06 Dec 2007 17:48 GMT
Well, why use NANT still and why not use MSBuild directly?

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
> Hi Nicholas,
> The problem is that we are migrating from .NET 1.1 to .NET 2.0, and we
[quoted text clipped - 50 lines]
>>
>> - Show quoted text -
Arne Vajhøj - 08 Dec 2007 04:18 GMT
> Well, why use NANT still and why not use MSBuild directly?
Maybe he likes NAnt.
I assume that NAnt still has way more tasks than MSBuild.
Arne