[Mono-list] Nunit2.0 from Mono code problems and success from Nunit 2.1.4 codebase!!

Francisco Figueiredo Jr. fxjrlists@yahoo.com.br
Sat, 20 Sep 2003 19:57:43 -0300


Gonzalo Paniagua Javier wrote:
> El sáb, 20-09-2003 a las 05:33, Francisco Figueiredo Jr. escribió:
> 
> 
> 
> NUnit uses Assembly.Load. That means that you have the assembly you want
> to run must be in your MONO_PATH, ie, in your case,
> MONO_PATH=.:$MONO_PATH
> 

Hi Gonzalo.
When I set MONO_PATH I got the following messages:

[fxjr@mercurio nunit2tests]$ export 
MONO_PATH=.:$MONO_PATH:/home/fxjr/Desenvolvimento/CVSRepositories/Mono/install/lib:/home/fxjr/Desenvolvimento/CVSRepositories/Mono/install/bin
[fxjr@mercurio nunit2tests]$ mono `which nunit-console.exe` 
NpgsqlTests.dll NUnit version 2.0.9 Copyright (C) 2002 James W. Newkirk, 
Michael C. Two, Alexei A. Vorontsov.
Copyright (C) 2000-2002 Philip Craig.
All Rights Reserved.

** 
(/home/fxjr/Desenvolvimento/CVSRepositories/Mono/install/bin/nunit-console.exe:3844): 
WARNING **: Could not find assembly nunit.framework

** 
(/home/fxjr/Desenvolvimento/CVSRepositories/Mono/install/bin/nunit-console.exe:3844): 
WARNING **: Could not find assembly nunit.framework

** 
(/home/fxjr/Desenvolvimento/CVSRepositories/Mono/install/bin/nunit-console.exe:3844): 
WARNING **: Could not find assembly nunit.framework

** 
(/home/fxjr/Desenvolvimento/CVSRepositories/Mono/install/bin/nunit-console.exe:3844): 
WARNING **: Could not find assembly nunit.framework

** 
(/home/fxjr/Desenvolvimento/CVSRepositories/Mono/install/bin/nunit-console.exe:3844): 
WARNING **: Could not find assembly nunit.framework

** 
(/home/fxjr/Desenvolvimento/CVSRepositories/Mono/install/bin/nunit-console.exe:3844): 
WARNING **: Could not find assembly nunit.framework

** 
(/home/fxjr/Desenvolvimento/CVSRepositories/Mono/install/bin/nunit-console.exe:3844): 
WARNING **: Could not find assembly nunit.framework

Unhandled Exception: System.IO.FileNotFoundException: File 'NpgsqlTests' 
not found.
in <0x001da> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke 
(System.Runtime.Remoting.Proxies.RealProxy,System.Runtime.Remoting.Messaging.IMessage,System.Exception&,object[]&)
in (unmanaged) (wrapper remoting-invoke) System.AppDomain:DoCallBack 
(System.CrossAppDomainDelegate)
in <0x00004> (wrapper remoting-invoke) System.AppDomain:DoCallBack 
(System.CrossAppDomainDelegate)
in <0x00032> (wrapper remoting-invoke-with-check) 
System.AppDomain:DoCallBack (System.CrossAppDomainDelegate)
in <0x0012a> NUnit.Framework.TestDomain:MakeRemoteTestRunner 
(System.IO.FileInfo,System.AppDomain)
in <0x00092> NUnit.Framework.TestDomain:Load (string)
in <0x000db> NUnit.Framework.TestDomain:Load (string)
in <0x00091> NUnit.Console.ConsoleUi:MakeTestFromCommandLine 
(NUnit.Framework.TestDomain,NUnit.Util.ConsoleOptions)
in <0x001c2> NUnit.Console.ConsoleUi:Main (string[])

GC Warning: Finalization cycle involving 807ef00


The strange part is that it used to work without have to specify any 
MONO_PATH. I already used it many times before. I used to use it in 
Cygwin, but now I'm using RedHat9.


Thanks in advance.

-- 
Regards,

Francisco Figueiredo Jr.

------
"My grandfather once told me that there are two
kinds of people: those
who work and those who take the credit. He told me
to try to be in the
first group; there was less competition there."
- Indira Gandhi