I've developed and am using a NAnt custom task that separates the sln and the proj as follows:
x calls separate task for each project found in sln--and allows specifying a default .build file for use on a per-proj basis, thus separating project-wide .build file from per-project build file(s)
Matthew
Mastracci wrote:
Perhaps it might be better to design an .xsd and use the automatic XML
deserialization routines. I've found that this way is much cleaner
than the methods used in the current and
tasks.
Using the xml de-/serialization way is fine
for .csproj,
but I don't see th
Thursday, July 24, 2003 11:35 PM
*To:* [EMAIL PROTECTED]
*Subject:* Re: [nant-dev] Solution/Project Parser
From reading the response posts I think I didn't make myself quiet
clear.
First of all what I'm suggesting is only of interest (I think) for
the VS.NET solut
Bernard
-Original Message-From: Yves Reynhout
[mailto:[EMAIL PROTECTED] Sent: Thursday, July 24, 2003 11:35
PMTo: [EMAIL PROTECTED]Subject: Re:
[nant-dev] Solution/Project Parser
From reading the response posts I think I
didn't make myself quiet clear.
First of all what I&
That makes things much more clear for me, and it sounds
like a great idea.
From: Yves Reynhout [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 4:35 PMTo:
[EMAIL PROTECTED]Subject: Re: [nant-dev]
Solution/Project Parser
From reading the response posts I think I
didn't make m
From reading the response posts I think I
didn't make myself quiet clear.
First of all what I'm suggesting is only of
interest (I think) for the VS.NET solution/project camp. I have not found
a library yet that allows me to parse VS.NET solution (.sln) and/or project
(.csproj) files, and ge
Tomas Restrepo; [EMAIL PROTECTED]
Subject: RE: [nant-dev] Solution/Project Parser
In the event that this is useful to others, I have attached the project
we use to make VS.NET 2003 "integrate" with NAnt. It's a VS.Net 2003
C++ "Makefile" project. The way it works is tha
It saves them all. One other good side effect of having output go to the output window
is context sensitivity for the errors/warnings on output of csc. You can click on the
output line and get VS.NET takes you to the source line.
-bc
-- Original Message -
Does VS.NET save all of your files before doing a build, or do you have
to manually save them?
Bill Conroy wrote:
My whole team does this all too.
Here is the writeup I gave out a while back to the OT list on how to do this:
Here are the steps I used to integrate[note I do not address keeping
> Every developer (the main dev team has about 8 people) builds
> directly with
> nant everytime (one of my coworkers came up with the idea to
> add a custom
> tool to vs.net that fires nant for the project and puts the
> nant output in
> the vs.net output window. nifty!).
How does one go about
OTECTED]
Sent: Thursday, July 24, 2003 11:32 AM
To: [EMAIL PROTECTED]
Subject: Re: [nant-dev] Solution/Project Parser
Matthew,
> I'm also getting close to wanting to use NAnt completely within the
> build process.
We do this for our project. We actually went a little bit further,a
My whole team does this all too.
Here is the writeup I gave out a while back to the OT list on how to do this:
Here are the steps I used to integrate[note I do not address keeping a
csproj in sync with the build file, but I could]
Do this once:
1. Add an external tool
Title: Nant (Current Proje
Matthew,
> I'm also getting close to wanting to use NAnt completely within the
> build process.
We do this for our project. We actually went a little bit further,and we
actually have a single VS.NET solution and project that *never* get built,
it's just for intellisense and the vs.net VSS integra
he .csproj files have become little more than the holders
of file lists and no longer the holder of build settings.
*From:* Yves Reynhout [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, July 22, 2003 5:02 PM
*To:* [EMAIL PROT
No problem. I'm all for refactoring the solution task. It's not an
elegant solution for what it accomplishes. My overall goal for the
solution task is to be able to point it at either a solution or a group
of projects and have them built in the correct order, with outputs
identical to how VS
build settings.
From: Yves Reynhout
[mailto:[EMAIL PROTECTED] Sent: Tuesday, July 22, 2003 5:02
PMTo: [EMAIL PROTECTED]Subject:
[nant-dev] Solution/Project Parser
Hi,
I've been following (though I should admit
not very actively using) NAnt for a while now (about 1200 nant posts in my
i
Hi,
I've been following (though I should admit
not very actively using) NAnt for a while now (about 1200 nant posts in my
inbox) . Especially, not being able to handle the VS.NET "solution"
concept was something that bothered me (well, let me rephrase: not handled
elegantly). Ofcourse, i
17 matches
Mail list logo
