date:20051013

[nant-dev] [ nant-Bugs-1082374 ] solution target and vcproj support for custom build steps

2005-10-13 Thread SourceForge.net

Bugs item #1082374, was opened at 2004-12-09 18:56
Message generated for change (Comment added) made by jensbr
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1082374group_id=31650

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Tom McAnnally (tmcannally)
Assigned to: Nobody/Anonymous (nobody)
Summary: solution target and vcproj support for custom build steps

Initial Comment:
When you have a vc project with a custom build step 
specified, the custom build step is not executed as 
would normally occur if you run the build from the 
Development environment.

I tested this on Visual Studio 2003.

Attached is a project that can be used to reproduce the 
issue.

This project should run the following command.

echo This is a custom build step  buildoutput.txt

to produce a build output of buildoutput.txt

Custom build steps can also have input files.

In this case the input file is input.txt.

Download the example and build midltest.build to 
reproduce the issue.

--

Comment By: Jens Bräuer (jensbr)
Date: 2005-10-13 12:08

Message:
Logged In: YES 
user_id=480617

Just wanted to ask, whether there is any progress for this
bug. At the moment the solution-task is the only advantage
of nant over ant (as far i am concerned). So this is a
blocker for me...

nevertheless for a version 0.85 nant look really great.


--

Comment By: Derek Hofmann (traal42)
Date: 2005-09-29 00:53

Message:
Logged In: YES 
user_id=662400

I too have a .vcproj file with a custom build step that could 
benefit from this.

--

Comment By: Matt Trentini (matt_trentini)
Date: 2005-08-08 09:18

Message:
Logged In: YES 
user_id=667724

Heya Guys,

Just adding my request for this feature - it's a show
stopper for me for the solution task (forcing me to instead
use exec/devenv).

Also, don't forget that not just projects can have custom
build steps - so can individual _files_.

Thanks,
Matt

--

Comment By: Andrea Barbieri (abarbieri)
Date: 2005-07-20 22:14

Message:
Logged In: YES 
user_id=65472

Hello

any idea if we are getting near a fix?

many thanks

--

Comment By: Gert Driesen (drieseng)
Date: 2005-01-24 19:23

Message:
Logged In: YES 
user_id=707851

I recently did some refactoring that should allow us to 
implement a fix for this issue. But I didn't yet have time for it.

I did implement support for project-level build events, though.

I'll let you know when something hits cvs (and the nightly 
builds).

--

Comment By: Tom McAnnally (tmcannally)
Date: 2005-01-24 19:15

Message:
Logged In: YES 
user_id=1175155

I have seen no action on this.  Just wondering if anything has 
been done with it.

--

Comment By: Gert Driesen (drieseng)
Date: 2004-12-14 16:18

Message:
Logged In: YES 
user_id=707851

Tom,

I've asked Simon if he can have a look at this issue, but I 
can't promise anything right now.

Gert

--

Comment By: Tom McAnnally (tmcannally)
Date: 2004-12-14 16:10

Message:
Logged In: YES 
user_id=1175155

I have seen lots of activity with vcproj issues, is anyone 
looking at this issue?

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1082374group_id=31650


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-1325875 ] TargetInvocationException using NUnit2 task

2005-10-13 Thread SourceForge.net

Bugs item #1325875, was opened at 2005-10-13 14:27
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1325875group_id=31650

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Tasks
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter McEvoy (pmcevoy)
Assigned to: Nobody/Anonymous (nobody)
Summary: TargetInvocationException using NUnit2 task

Initial Comment:
Hi Everyone,
Windows 2000, .Net 1.1, nant-0.85-nightly-2005-10-11,
nunit2.2

I'm getting a TargetInvocationException when using nant
to run NUnit2 tasks against assemblies that contain J#
code.

I believe that the cause is due to
http://support.microsoft.com/?kbid=830297 in that when
an appdomain with J# code is unloaded, stdout gets
closed, which Nant then tries to write log messages to.  

I have attached a simple solution that demonstrates the
problem when executed with the nunit2 task (build the
solution, then execute the tests using nant and the
included nant.build).  

I have also attached a fix to NUnit2TestDomain.cs
which allows nant to continue and run all tests -
although I have no doubt that the nant devs will have a
much more elegant solution than my paltry attempt ;-)

I hope that this (or better) solution can be applied to
the source tree, as I really don't want to be working
from my own personal forked version of the nant code...

Sincerely
Pete

Addendum:  I wanted to attach two files, but it does'nt
look like I can on SF...  here are the changes I made
to NUnit2TestDomain.cs:

public void Unload() {
if (_domain != null) {
try {
AppDomain.Unload(_domain);

//Due to bug
http://support.microsoft.com/?kbid=830297, any
assemblies containing
//J# code referenced in the unit test will cause
stdout to get closed when the AppDomain
//is unloaded - this code just reopens stdout and
allows nant to continue
StreamWriter standardOutput = new
StreamWriter(Console.OpenStandardOutput());

standardOutput.AutoFlush = true;
Console.SetOut(standardOutput);
} catch (CannotUnloadAppDomainException) {
// ignore exceptions during unload, this matches the 
// behaviour of the NUnit TestDomain
} finally {
_domain = null;
}
}
}


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1325875group_id=31650


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-1325875 ] TargetInvocationException using NUnit2 task

2005-10-13 Thread SourceForge.net

Bugs item #1325875, was opened at 2005-10-13 14:27
Message generated for change (Comment added) made by pmcevoy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1325875group_id=31650

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Tasks
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter McEvoy (pmcevoy)
Assigned to: Nobody/Anonymous (nobody)
Summary: TargetInvocationException using NUnit2 task

Initial Comment:
Hi Everyone,
Windows 2000, .Net 1.1, nant-0.85-nightly-2005-10-11,
nunit2.2

I'm getting a TargetInvocationException when using nant
to run NUnit2 tasks against assemblies that contain J#
code.

I believe that the cause is due to
http://support.microsoft.com/?kbid=830297 in that when
an appdomain with J# code is unloaded, stdout gets
closed, which Nant then tries to write log messages to.  

I have attached a simple solution that demonstrates the
problem when executed with the nunit2 task (build the
solution, then execute the tests using nant and the
included nant.build).  

I have also attached a fix to NUnit2TestDomain.cs
which allows nant to continue and run all tests -
although I have no doubt that the nant devs will have a
much more elegant solution than my paltry attempt ;-)

I hope that this (or better) solution can be applied to
the source tree, as I really don't want to be working
from my own personal forked version of the nant code...

Sincerely
Pete

Addendum:  I wanted to attach two files, but it does'nt
look like I can on SF...  here are the changes I made
to NUnit2TestDomain.cs:

public void Unload() {
if (_domain != null) {
try {
AppDomain.Unload(_domain);

//Due to bug
http://support.microsoft.com/?kbid=830297, any
assemblies containing
//J# code referenced in the unit test will cause
stdout to get closed when the AppDomain
//is unloaded - this code just reopens stdout and
allows nant to continue
StreamWriter standardOutput = new
StreamWriter(Console.OpenStandardOutput());

standardOutput.AutoFlush = true;
Console.SetOut(standardOutput);
} catch (CannotUnloadAppDomainException) {
// ignore exceptions during unload, this matches the 
// behaviour of the NUnit TestDomain
} finally {
_domain = null;
}
}
}


--

Comment By: Peter McEvoy (pmcevoy)
Date: 2005-10-13 14:29

Message:
Logged In: YES 
user_id=36439

Ah... it seems you can add a second file via the comments...

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1325875group_id=31650


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] internal error when using nunit.....

2005-10-13 Thread Dean Hiller

Maybe this bug is already fixed. If so, please let me know.
Otherwise, is there any way to work around this?

I am using this version of ant

NAnt 0.85 (Build 0.85.1869.0; rc2; 2/12/2005)

It told me to email you this report.

nunit:

BUILD FAILED

INTERNAL ERROR

System.IO.FileNotFoundException: File or assembly name nunit.core,
or one of its

dependencies, was not found.

File name: nunit.core

at NAnt.NUnit2.Tasks.NUnit2Task.ExecuteTask()

at NAnt.Core.Task.Execute()

at NAnt.Core.Target.Execute()

at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)

at NAnt.Core.Project.Execute()

at NAnt.Core.Project.Run()

=== Pre-bind state information ===

LOG: DisplayName = nunit.core, Version=2.2.0.0,
Culture=neutral, PublicKeyToken=

96d09a1eb7f44a77

(Fully-specified)

LOG: Appbase =
C:\AROOT\views\workviews\hsem40\common\framework\input\tools\nant

LOG: Initial PrivatePath = NULL

Calling assembly : NAnt.NUnit2Tasks, Version=0.85.1869.0,
Culture=neutral, Publi

cKeyToken=null.

===

LOG: Private path hint found in configuration file: lib.

LOG: Publisher policy file is not found.

LOG: Host configuration file not found.

LOG: Using machine configuration file from
C:\WINNT\Microsoft.NET\Framework\v1.1

.4322\config\machine.config.

LOG: Post-policy reference: nunit.core, Version=2.2.0.0,
Culture=neutral, Public

KeyToken=96d09a1eb7f44a77

LOG: Attempting download of new URL file:///C:/AROOT/views/workviews/hsem40/comm

on/framework/input/tools/nant/nunit.core.DLL.