Re: GCHandle exception (appdomain related?) (was: Re: [Partly-SOLVED!] Re: Output from Console.WriteLine methods is deferred)

"Charlie Poole" <[email protected]> Sun, 20 Jul 2008 17:28:39 -0700
Newsgroups gmane.comp.windows.dotnet.nunit.user
Message-ID <000001c8eac8$c4ecef40$6401a8c0@ferrari>
Hi Andres, 

> > Domain=none is a hack that most people should never use. It was 
> > created for one user, with code that could not even execute 
> correctly 
> > in a secondary AppDomain.
> 
> Heh, it turns out that maybe it will be useful for me too.

Too bad for you :-( 

> > Since there is only one domain, there is only one 
> application base and 
> > config file. To use it, you must copy the NUnit itself to the 
> > directory containing your test assembly. Any entries you would 
> > normally put in a test config file must go in the nunit config.
> 
> Oh! Thanks for the info! Maybe we should then improve the 
> output of that case, regardless it's an undocumented feature, right?

No, it's mentionned in the docs - just not well-documented.
 
> BTW, on a side note, why does the domain=none environment 
> require this kind of thing? AFAIK, there are ways to load 
> assemblies in the same app-domain without requiring them to 
> be in the same dir (that's what MonoAddins does IIRC). Can't 
> we use this kind of thing for this case?

NUnit tries to avoid using the LoadFrom environment because of
the problems that causes when the user test wants to load 
dependencies in the normal Load environment. (It may be that
these problems only exist in Windows, but they are documented
there with lots of warnings against using LoadFrom.)

I'm hoping to get some ideas out of mono.addins as I get
further into it. In fact, mono-addins will handle addins
in 3.0, so that will take care of a good part of the load
problem. Essentially, a lot of what we now do comes is
historical in origin, but it's hard to change behavior when
a lot of people depend on the applicaton. Remember, it has
to work on CLRs from 1.0 through 3.5, on Windows and Linux,
etc. - it's hard to change fundamental behavior. 

Which is why I look forward to making a break with 3.0. :-) 

Charlie

> Regards,
> 
> 	Andrés
> 
> -- 
> 
> 
> --------------------------------------------------------------
> -----------
> This SF.Net email is sponsored by the Moblin Your Move 
> Developer's challenge Build the coolest Linux based 
> applications with Moblin SDK & win great prizes Grand prize 
> is a trip for two to an Open Source event anywhere in the 
> world http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Nunit-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nunit-users
> 


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/