Hi,
some time ago there was discussion that <solution>
task could have something like <project-overrides> which could override
some properties for all or some projects in the solution. I think this could be
handy sometimes, since many of us (incl. me) workarounds it todays by modifying
.csproj (.vsproj)'s which is pretty easy but no very clean.
What you think about this approach?
|
GORDIC spol. s. r.o., Erbenova 4, 586 01 JIHLAVA Tel: 567 309 136, 567 303 601 |
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gert Driesen
Sent: Thursday, February 24, 2005 7:41 AM
To: 'Vojtech Jakes'; nant-developers@lists.sourceforge.net
Subject: RE: [nant-dev] Solution-optional paramHi Vojta,Not sure if this is something we want. IF we add this, then I'm pretty sure we'll end up with 100 attributes controlling the behavior of the <solution> task, while its really intended to mimic the behavior of VS.NET.People that need more control, could use the individual compiler tasks.You were planning on submitting more changes to the VC++ support in the <solution> task, right ? Made any progress ?Gert
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vojtech Jakes
Sent: woensdag 23 februari 2005 21:26
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] Solution-optional paramHi,has anyone considered adding a boolean parameter to the solution task forcing the creation of XML documentation on C# projects? This could be really quick one I think...CheersVojta
________________________________________________________________________
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]
This email has been scanned for all viruses by the FFastFill Email
Security System.
________________________________________________________________________
<<gordic.gif>>
