Hi Scott,
The following is an example of a build that I perform:
!-- Core infrastructure components --
target name=level1
csc target=library output=Core.dll
sources
includes name=*.cs/
/sources
/csc
... other base
Scott,
Yes, the fork option was removed and made the default(sort of). Now (as of
oct I think) nunit2 tests create a new appdomain to execute in.
Indeed, this should be how it always works, now (assuming nobody undid the
changes I made last time to it g). It's worthwhile to notice that this
True. It took me a little while to see this. But now I understand things
much better. And I think I better understand where some of the issues are
coming from.
In addition to the changes you made, I think we need to set the environment
working/current directory to the nunit2 basedir. This will
Yeah, I'm there with you, maybe some documentation would solve this problem.
Also, maybe this isn't the optimal solution, but we could add an option to
change the current directory if you want to have the current env dir set.
As long as we differ from the NUnit console/gui, there will be
