Re: [NAnt-users] Why aren't Nant / NantContrib Assemblies signed

2007-04-10 Thread Jay Walker
Gert, Signing assemblies is an ambiguous term that can mean applying a strong name to the assembly or verifying the publisher. I am referring to applying a strong name. We don't store the assemblies in the GAC. Currently, we just extend some tasks to better suit our environment and we sign (with

Re: [NAnt-users] Why aren't Nant / NantContrib Assemblies signed

2007-04-10 Thread Bob Archer
I'd rather see the "official" assemblies not signed. One issue is the version probing that signing adds to the assembly. Although this is admittedly a smaller issue for Nant since most people don't reference Nant's binaries unless they are extending Nant. BOb -Original Message- From: [EM

Re: [NAnt-users] Why aren't Nant / NantContrib Assemblies signed

2007-04-10 Thread Jay Walker
Gert, Signing assemblies is an ambiguous term that can mean applying a strong name to the assembly or verifying the publisher. I am referring to applying a strong name. We don't store the assemblies in the GAC. Currently, we just extend some tasks to better suit our environment and we sign (with

Re: [NAnt-users] Why aren't Nant / NantContrib Assemblies signed

2007-04-10 Thread Evans, Jonathan (2)
This is a contentious point. Signing serves several purposes: 1) It implies a degree of security in that in a closed-source model theoretically only the original vendor is able to sign their assemblies; 2) It is part of a type's identifier and so suggests an adherence to a particular interfa

Re: [NAnt-users] Why aren't Nant / NantContrib Assemblies signed

2007-04-10 Thread Gert Driesen
Jay, In general, you sign assemblies because: a) you want to to store them in the GAC => we don't see an immediate need to store our assemblies in the GAC b) to allow users to verify the publisher => our signing key would need to be public to allow users to build NAnt from source; hence anyone

Re: [NAnt-users] Why aren't Nant / NantContrib Assemblies signed

2007-04-10 Thread Jay Walker
Nunit is open source and the source is hosted on sourceforge. The NUnit project provides a signing key (nunit.snk) as part of the source release. The hosted build that publishes the binary release uses this key to sign the assemblies. You can use the provided key for your own 'bug fix' builds from

Re: [NAnt-users] Email notification on Nunit failures

2007-04-10 Thread Nikesh Patel
Cheers for that, it helped alot. The problem i'm having now is that each of the NUnit tests are in their respective build file which i then call from the main build file. What i want to do is send a seperate mail for each of the indiviual build files so it only contains information on just NUnits

Re: [NAnt-users] passing string delimiters

2007-04-10 Thread Phil Sayers
(blush) operator error. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brass Tilde Sent: Tuesday, April 10, 2007 10:11 AM To: nant-users@lists.sourceforge.net Subject: Re: [NAnt-users] passing string delimiters Phil Sayers <[EMAIL PROTECTED]> wrote: > w

Re: [NAnt-users] passing string delimiters

2007-04-10 Thread Brass Tilde
Phil Sayers <[EMAIL PROTECTED]> wrote: > with MSBuild you must delimit the project or solution path/name with > quotes otherwise you get > MSBUILD : error MSB1008 I've never gotten that error from using the MSBuild task. But you used single quotation marks. Should you be using double quotation

Re: [NAnt-users] passing string delimiters

2007-04-10 Thread Gert Driesen
- Original Message - From: "Brass Tilde" <[EMAIL PROTECTED]> To: "Phil Sayers" <[EMAIL PROTECTED]>; Sent: Tuesday, April 10, 2007 3:15 PM Subject: Re: [NAnt-users] passing string delimiters > Phil Sayers <[EMAIL PROTECTED]> wrote: > >>> ok, >>> I'm using the msbuild task from nantContr

Re: [NAnt-users] passing string delimiters

2007-04-10 Thread Phil Sayers
dangit whadda ya knowi coulda sworn i removed them single quotesoh well. thanks anywany -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gert Driesen Sent: Tuesday, April 10, 2007 9:25 AM To: Brass Tilde; Phil Sayers; nant-users@lists.sourceforge.n

Re: [NAnt-users] passing string delimiters

2007-04-10 Thread Phil Sayers
with MSBuild you must delimit the project or solution path/name with quotes otherwise you get MSBUILD : error MSB1008 i'll wait on the bugfix. thanks gert. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brass Tilde Sent: Tuesday, April 10, 2007 9:15 AM To:

Re: [NAnt-users] passing string delimiters

2007-04-10 Thread Mark Modrall
How about reversing the wrapping (i.e. '"Solution 1.sln"' instead of "'Solution 1.sln'"). Xml lets you quote attributes with either an apostrophe or a quote mark. If you put the double quotes inside the attribute declaration, the xml processor will take care of it and the nant plugins probably won'

Re: [NAnt-users] passing string delimiters

2007-04-10 Thread Brass Tilde
Phil Sayers <[EMAIL PROTECTED]> wrote: >> ok, >> I'm using the msbuild task from nantContrib, but i'm sure the same >> principles apply to nant, it's just a syntax issue. >> >> so my msbuild task looks like this >> >> < msbuild project="'${core.source}\Solution 1.sln'" > I've never had to include

Re: [NAnt-users] passing string delimiters

2007-04-10 Thread Gert Driesen
- Original Message - From: "Phil Sayers" <[EMAIL PROTECTED]> To: Sent: Tuesday, April 10, 2007 2:56 PM Subject: [NAnt-users] passing string delimiters > ok, > I'm using the msbuild task from nantContrib, but i'm sure the same > principles apply to nant, it's just a syntax issue. > > so

[NAnt-users] passing string delimiters

2007-04-10 Thread Phil Sayers
ok, I'm using the msbuild task from nantContrib, but i'm sure the same principles apply to nant, it's just a syntax issue. so my msbuild task looks like this < msbuild project="'${core.source}\Solution 1.sln'" > < arg line="OutputDir=${core.output}\" /> < arg line="Configuration=Debug" />