thanks for the response.
Yes, the project does compile fine in VS. What I meant regarding hte
.sln files is that (I'm new to VS so I'm not too good with the
terminology yet) when I build the Source.sln in VS, I can see it calling and
building all these sub-projects in the output window on the bottom of hte
screen, like Mathlib and such. For instance, there's a ScenarioBuilder
folder in the same directory as Source.sln, and for a build of
Source.sln I need to get it (scenariobuilder) cleaned and compiled. Do I
include "ScenarioBuilder\Scenario.vcproj" in a "<projects>" tag within
"<solution>" or will the solution task automatically see the dependency and
do it for me. Without any project or referencs tags, my build file is
loading all the required *.vcproj's that I need, but since my build is
crashing I'm not sure if i have to include something else as well...
I'm doing what you sug gested and using the <delete> to clean my output
files. It wasn't as bad as I thought it would be. thanks.
Yes, the project does compile fine in VS. What I meant regarding hte
.sln files is that (I'm new to VS so I'm not too good with the
terminology yet) when I build the Source.sln in VS, I can see it calling and
building all these sub-projects in the output window on the bottom of hte
screen, like Mathlib and such. For instance, there's a ScenarioBuilder
folder in the same directory as Source.sln, and for a build of
Source.sln I need to get it (scenariobuilder) cleaned and compiled. Do I
include "ScenarioBuilder\Scenario.vcproj" in a "<projects>" tag within
"<solution>" or will the solution task automatically see the dependency and
do it for me. Without any project or referencs tags, my build file is
loading all the required *.vcproj's that I need, but since my build is
crashing I'm not sure if i have to include something else as well...
I'm doing what you sug gested and using the <delete> to clean my output
files. It wasn't as bad as I thought it would be. thanks.
John Ludlow <[EMAIL PROTECTED]> wrote:
Hi, Pat
What exactly do you mean when you say that your Source.sln project
requires the others? Do you mean that you selected the other .sln files as
references? In this case VS just looks at the .sln youve selected and
creates references to the projects, meaning the <solution> task will
know how to build them. If, however, its some funky dependency thats
not recognised in the .sln, then youll need a separate <solution> task
for each one. Whether you want a separate build file for each one
under that circumstance is up to you NAnt handles multiple <solution>
tasks with no problem, but this is not always good practice.
The best way of doing a clean, Ive found, is using the <delete> task.
The good thing is this also handles any confusion that the SCM system
has over file status (we use StarTeam which has been known to get in a
bit of a muddle over that, the poor thing). Just deleting all the files
from your build folder will just mean everything is starting from the
same point each build a good thing, IMHO.
As for your linking problem, I dont know. Does it compile in VS.NET?
If so it may be a bug in NAnt. It looks like VC++ to me, which I
generally avoid like a thing to be actively avoided. Saying avoid like the
plague somehow doesnt quite describe it. ;)
John
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football