[nant-dev] nunit appdomain leak?

[Nat Luengnaruemitchai]

Hi,

I have a project 
where I have multiple projects. In each one, it has its own unit tests. After I 
upgrade my NANT to use the latest nightly (to be able to run .NET 2.0), I found 
that nunit2 task will create appmain for each dll in each project and for some 
reasons, I found that the app domain is still in memory. They didn't get clear 
out from NANT.exe process properly. Anyone experienced the same 
problem?

Nat

[nant-dev] Detect Error But Still Continue The Build

[Nat Luengnaruemitchai]

Hi,

I have a problem in 
handling errors inside NAnt script. Basically, I have many C++ code and I have 
to compile it with different options for some groups of files. Therefore, I 
might need to call "cc" task a couple times. If one of them fails, I would like 
to continue to compile the next groups of files until it finishes and then fail 
the whole process later. Is there any workaround to allow that? As I look into 
the code, when the failonerror flag set to false, only logging has been done. It 
might make sense if some flags/properties are set.

Thanks,
Nat

[nant-dev] NAnt Compiler Option

[Nat Luengnaruemitchai]

Inside ClTask.cs, there are a couple lines of code which enforce the
output and symbol files when compile C++ code as follows:

   writer.WriteLine(/Fd\{0}{1}\, OutputDir.FullName, 
Path.AltDirectorySeparatorChar);
writer.WriteLine(/Fo\{0}{1}\, OutputDir.FullName, 
Path.AltDirectorySeparatorChar);

This code overrides user-specified option such that build script
cannot enforce the output (*.obj) and debug symbol (*.pdb) filename
manually. Is it possible to allow that to happen?

Thanks,
Nat


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Scope property

[Nat Luengnaruemitchai]

Hi,

Is it possible to have a scope property such that it will be available
only in the scope and anything below that?

For example,

Target A calls Target B,C
and Target B calls Target BB
and Target C calls Target CC

If a property is defined in Target B, Target B and BB will see it
while Target C won't see the property defined in Target B

Nat


---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] FW: cvs-checkout bug

[Nat Luengnaruemitchai]

In CheckoutTask.cs under 
/src/NAnt.SourceControl,

line 81: 
 public const string CvsCommandName = 
"update";
should 
be


line 81: 
 public const string CvsCommandName = 
"checkout";
Otherwise, the code 
will not be checked out properly.

In addition to 
that,I guessthat the code hasn't been fully refactored as 
AbstractSourceControlTask.cs still depends on UpdateTask.cs

Thanks,
Nat

RE: [nant-dev] FW: cvs-checkout bug

[Nat Luengnaruemitchai]

Title: RE: [nant-dev] FW: cvs-checkout bug






AbstrackSourceControl refers to UpdateTask.CommandName. I'm not sure whether it should be that way. I guess it can be refactored but not necessary.

Nat


-Original Message-

From: Clayton Harbour [mailto:[EMAIL PROTECTED]] 

Sent: Wednesday, May 26, 2004 10:12 AM

To: Nat Luengnaruemitchai; [EMAIL PROTECTED]

Subject: RE: [nant-dev] FW: cvs-checkout bug


Hi Nat,


Thanks for the report, the first issue has been fixed in cvs now. I am not sure what you mean about AbstractSourceControl.cs depending on UpdateTask.cs, can you please explain further? 


Cheers,



Clayton



-Original Message-

From: Nat Luengnaruemitchai [mailto:[EMAIL PROTECTED]]

Sent: Tue 5/25/2004 7:43 AM

To: [EMAIL PROTECTED]

Cc: 

Subject: [nant-dev] FW: cvs-checkout bug

In CheckoutTask.cs under /src/NAnt.SourceControl,



line 81: public const string CvsCommandName = update;


should be



line 81: public const string CvsCommandName = checkout;


Otherwise, the code will not be checked out properly.



In addition to that, I guess that the code hasn't been fully refactored as AbstractSourceControlTask.cs still depends on UpdateTask.cs



Thanks,

Nat