Gert,
I guess I'll just have to
keep a private copy on NAnt with these changes in it. We have over 100 csproj
files (in about 30 solutions) to build our entire project.
The solution task was the easy way to still
have just one file that listed the project properties (the .csproj file) for
each project that is used by both the developer and the automated build process.
Keeping two files in sync (the csproj file and a
seprate NAnt build file using the compiler tasks) is just not
feasible.
Our need was to be able to have pdb files
for the release build so we could use tools like ncover. We discovered that
VS.NET does not support the pdbonly option directly os the solution task did not
either.
Anyway - thanks
Brian
From: Gert Driesen
[mailto:[EMAIL PROTECTED]Sent: Sat 3/5/2005 8:43
AMTo: Walker, Brian;
nant-developers@lists.sourceforge.netSubject: RE: [nant-dev] Patch
for 1156702
Brian,
I'm afraid this is
not something we'll support in the task. If we start
adding switches like this one, then we end up with something that is no longer
controllable.
If you really need
lots of flexibility, then I'd suggest using our individual compiler
tasks.
I've
just added support for the different debug types to cvs. Before this change, our compiler tasks only
supported either full debug output or no debug output at
all.
I really hope you understand
! We might look into a more configurable
task after the 0.85 release, but no promises there
...
Gert
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Walker, BrianSent: vrijdag 4 maart 2005 19:22To:
nant-developers@lists.sourceforge.netSubject: [nant-dev] Patch for
1156702
This is a patch for bug
1156702.
It adds the “releasesymbols”
attribute to the solution task. If set to true and a project in the solution
is set to not generate debug information (DebugSymbols is false) then it sets
the debug setting to “/debug:pdbonly” instead of “/debug-“. This will generate
the pdb file but otherwise leave the assembly as a release build (no
debuggable attribute added).
Brian Walker