[nant-dev] Just a suggestion...

2003-07-09 Thread Giuseppe Greco 
Hi all,

right now, the nunit2 task takes the following
form:

nunit2
  test assemblyname=${build.dir}/bin/MyModule.Tests.dll/
/nunit2

The task above doesn't test an 'assembly', but a 'module'.
One can create single-module assemblies or multi-module
assemblies, but a test task always tests a module.

So, I would suggest to rename the assemblyname property to
module:

nunit2
  test module=${build.dir}/bin/MyModule.Tests.dll/
/nunit2

What do you think about that?

Gius_.



---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing  more.
Download  eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

RE: [nant-dev] Just a suggestion...

2003-07-09 Thread Anthony LoveFrancisco 
What's your definition of module versus assembly ?

- Ants

|  -Original Message-
|  From: [EMAIL PROTECTED] 
|  [mailto:[EMAIL PROTECTED] On 
|  Behalf Of Giuseppe Greco
|  Sent: Wednesday, 09 July, 2003 00:57
|  To: [EMAIL PROTECTED]
|  Subject: [nant-dev] Just a suggestion...
|  
|  
|  Hi all,
|  
|  right now, the nunit2 task takes the following
|  form:
|  
|  nunit2
|test assemblyname=${build.dir}/bin/MyModule.Tests.dll/
|  /nunit2
|  
|  The task above doesn't test an 'assembly', but a 'module'.
|  One can create single-module assemblies or multi-module 
|  assemblies, but a test task always tests a module.
|  
|  So, I would suggest to rename the assemblyname property to
|  module:
|  
|  nunit2
|test module=${build.dir}/bin/MyModule.Tests.dll/
|  /nunit2
|  
|  What do you think about that?
|  
|  Gius_.
|  
|  
|  
|  ---
|  This SF.Net email sponsored by: Parasoft
|  Error proof Web apps, automate testing  more.
|  Download  eval WebKing and get a free book. 
|  www.parasoft.com/bulletproofapps 
|  ___
|  nant-developers mailing list [EMAIL PROTECTED]
|  https://lists.sourceforge.net/lists/listinfo/nant-developers
|  



---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing  more.
Download  eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Just a suggestion...

2003-07-09 Thread Ian MacLean 
To be honest the occurance of multi module assemblies is low enough that 
I think most users will find 'assembly' a more meaningful identifier 
than 'module'.
the Assembly.LoadFrom() method which loads a specific file off disk 
calls that file paramater 'assemblyFile' not 'moduleFile'. So I think we 
are safe enough using assembly.

Ian

Anthony LoveFrancisco wrote:

What's your definition of module versus assembly ?

- Ants

|  -Original Message-
|  From: [EMAIL PROTECTED] 
|  [mailto:[EMAIL PROTECTED] On 
|  Behalf Of Giuseppe Greco
|  Sent: Wednesday, 09 July, 2003 00:57
|  To: [EMAIL PROTECTED]
|  Subject: [nant-dev] Just a suggestion...
|  
|  
|  Hi all,
|  
|  right now, the nunit2 task takes the following
|  form:
|  
|  nunit2
|test assemblyname=${build.dir}/bin/MyModule.Tests.dll/
|  /nunit2
|  
|  The task above doesn't test an 'assembly', but a 'module'.
|  One can create single-module assemblies or multi-module 
|  assemblies, but a test task always tests a module.
|  
|  So, I would suggest to rename the assemblyname property to
|  module:
|  
|  nunit2
|test module=${build.dir}/bin/MyModule.Tests.dll/
|  /nunit2
|  
|  What do you think about that?
|  
|  Gius_.
|  
|  
|  
|  ---
|  This SF.Net email sponsored by: Parasoft
|  Error proof Web apps, automate testing  more.
|  Download  eval WebKing and get a free book. 
|  www.parasoft.com/bulletproofapps 
|  ___
|  nant-developers mailing list [EMAIL PROTECTED]
|  https://lists.sourceforge.net/lists/listinfo/nant-developers
|  



---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing  more.
Download  eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
 





---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing  more.
Download  eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Just a suggestion...

2003-07-09 Thread Giuseppe Greco 

-- Original Message --
From: Ian MacLean [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: 'Giuseppe Greco' [EMAIL PROTECTED],
   [EMAIL PROTECTED]
Subject: Re: [nant-dev] Just a suggestion...
Date: Thu, 10 Jul 2003 10:58:16 +0900


To be honest the occurance of multi module assemblies is low enough that

I think most users will find 'assembly' a more meaningful identifier 
than 'module'.
the Assembly.LoadFrom() method which loads a specific file off disk 
calls that file paramater 'assemblyFile' not 'moduleFile'. So I think we

are safe enough using assembly.

Ian

Anthony LoveFrancisco wrote:

What's your definition of module versus assembly ?

A module, is a single application component, while
an assembly  encloses all the modules (or component) that
form an application. When we run the test case, we are
actually testing a single application component, not
the whole application (assembly).

Gius_.


- Ants

|  -Original Message-
|  From: [EMAIL PROTECTED] 
|  [mailto:[EMAIL PROTECTED] On 
|  Behalf Of Giuseppe Greco
|  Sent: Wednesday, 09 July, 2003 00:57
|  To: [EMAIL PROTECTED]
|  Subject: [nant-dev] Just a suggestion...
|  
|  
|  Hi all,
|  
|  right now, the nunit2 task takes the following
|  form:
|  
|  nunit2
|test assemblyname=${build.dir}/bin/MyModule.Tests.dll/
|  /nunit2
|  
|  The task above doesn't test an 'assembly', but a 'module'.
|  One can create single-module assemblies or multi-module 
|  assemblies, but a test task always tests a module.
|  
|  So, I would suggest to rename the assemblyname property to
|  module:
|  
|  nunit2
|test module=${build.dir}/bin/MyModule.Tests.dll/
|  /nunit2
|  
|  What do you think about that?
|  
|  Gius_.
|  
|  
|  
|  ---
|  This SF.Net email sponsored by: Parasoft
|  Error proof Web apps, automate testing  more.
|  Download  eval WebKing and get a free book. 
|  www.parasoft.com/bulletproofapps 
|  ___
|  nant-developers mailing list [EMAIL PROTECTED]
|  https://lists.sourceforge.net/lists/listinfo/nant-developers
|  



---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing  more.
Download  eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
  





---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing  more.
Download  eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing  more.
Download  eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers