Re: [Mono-dev] runtime specification in nunit-console.exe.config

2005-10-24 Thread Kamil Skalski
Actually, as Sebastien mentioned in that thread, we cannot just
install the 2.0 nunit assemblies, because they conflict with 1.1
profile ones.
But indeed, removing .config file from nunit-console is a good idea,
because it is rather meaningless on mono (the corlib should be choosen
according to the profile for which nunit-console was compiled and
there are no 1.0 compatibility issue).
It is a safe operation and IMO can be commited immediately.

And about resolving assemblies conflict problem... I have an idea that:
- lib/mono/1.0  and lib/mono/2.0 directories would both contain
nunit.core.dll, etc. symlinks to the GAC, but there would be two kind
of directories in the gac/:
- nunit.core, nunit.framework,...  and nunit2.core, nunit2.framework, ...
- if it is possible, those *2.* directories would just be the
disambiguation hack and they would contain standard  nunit.core.dll,
nunit.framework.dll, ...
- there would be additional mono-nunit2.pc, which would point to 2.0 assemblies

This is my idea, but I'm not sure what Makefile stuff needs to be done
for such configuration and the most important thing, if gacutil allows
to create the mentioned hack directories.


2005/10/24, Atsushi Eno [EMAIL PROTECTED]:
 Oh, thanks Kamil, I overlooked the post... that patch looks cooler :-)
 I support it.

 Atsushi Eno

 Kamil Skalski wrote:
  Yap, removing this would be nice and it would bring nunit-console on
  2.0 profile one step closer to being usable outside the mono build
  tree (see 
  http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014598.html)
 
  This is a deviation from original nunit.org sources though.
 
  Still, the most difficult problem with nunit for 2.0 is that we need
  to store somehow the 2.0 version of nunit assemblies and the current
  versioning/numbering scheme does not give a clean way for this. Nunit
  assemblies are currently installed into the GAC under 2.2.0.0 version
  number (and are compiler for 1.1 profile).
 



--
Kamil Skalski
http://nazgul.omega.pl
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


Re: [Mono-dev] runtime specification in nunit-console.exe.config

2005-10-23 Thread Kamil Skalski
Yap, removing this would be nice and it would bring nunit-console on
2.0 profile one step closer to being usable outside the mono build
tree (see 
http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014598.html)

This is a deviation from original nunit.org sources though.

Still, the most difficult problem with nunit for 2.0 is that we need
to store somehow the 2.0 version of nunit assemblies and the current
versioning/numbering scheme does not give a clean way for this. Nunit
assemblies are currently installed into the GAC under 2.2.0.0 version
number (and are compiler for 1.1 profile).

2005/10/23, Atsushi Eno [EMAIL PROTECTED]:
 Hello,

 Do we have to specify supportedRuntime and requiredRuntime in
 nunit-console.exe.config?  If we omit those sections, we can run
 make PROFILE=net_2_0 run-test-ondotnet to verify our NUnit test
 sanity (i.e. check if they don't fail under .NET 2.0) on Windows.

 If there is no need, then the attached patch would make it possible.

 Atsushi Eno


 Index: nunit-console.exe.config
 ===
 --- nunit-console.exe.config(revision 52109)
 +++ nunit-console.exe.config(working copy)
 @@ -23,11 +23,13 @@
  --
startup

 +!--
   supportedRuntime version=v1.1.4322 /
   supportedRuntime version=v2.0.50215 /
   supportedRuntime version=v1.0.3705 /

   requiredRuntime version=v1.0.3705 /
 +--

/startup

 @@ -89,4 +91,4 @@

/runtime

 -/configuration
 \ No newline at end of file
 +/configuration

 ___
 Mono-devel-list mailing list
 Mono-devel-list@lists.ximian.com
 http://lists.ximian.com/mailman/listinfo/mono-devel-list





--
Kamil Skalski
http://nazgul.omega.pl
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list