I am at PDC and attended the session last night. The MSBuild is basically
NAnt with the following differences.
[1] Now the Visual Studio project file is the "build" file. This allows for
much tighter integration between VS and the build tool. In fact VS now
"shells" out to the build tool dir
It seems that a target will only get executed once in any project.
Example:
The output from this is
test:
[echo] in test
test1:
Take a look at the /imports switch. You can specify the assemblies there.
brant
...
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Nant-users digest, Vol 1 #168 - 1 msg
Date: Sat, 08 Mar 2003 12:21:33 -0800
Send Nant-users mailing list submissions to
I would hope that simply using NAnt does not require my product to be under
the same license as it.
brant
...
Message: 1
Date: Sun, 26 Jan 2003 11:04:18 -0800
From: "Clayton Harbour" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [Nant-users] License
Hi,
=20
I hope this has not a really
Klaus, there is a tool called Slingshot which with a bit of work will do
what you want. It will read your .sln files and generate nant compliant
.build files. You might also want to look at this article which provides a
different solution to the problem.
http://radio.weblogs.com/0106046/stori
I just downloaded the latest CVS source and was having trouble getting it to
work with my VB.NET projects. I have traced the problem to a recent
check-in.
Solution.cs Revision 1.4 added the following lines:
string commonProjectId = "{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}";
string enterprosePro
