[Mono-bugs] [Bug 76636][Nor] Changed - Runtime version selection is not MS.NET compatible

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by kornelpal at hotmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=76636

--- shadow/76636	2005-11-07 07:14:39.000000000 -0500
+++ shadow/76636.tmp.11884	2005-11-11 11:31:58.000000000 -0500
@@ -11,13 +11,13 @@
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: kornelpal at hotmail.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: Runtime and assembly version selection is not MS.NET compatible
+Summary: Runtime version selection is not MS.NET compatible
 
 MS.NET uses the available runtime with the lowest version number that is 
 greather than or equal to the runtime version of the executed image. This 
 behavior can be overriden using app.config. mscorlib.dll that belongs to 
 the selected runtime is loaded regardless of app.config. All other 
 assemblies are loaded using standard version matching even from the GAC. 
@@ -98,6 +98,15 @@
 managed applications.
 
 I think the solution is to use the runtime select behavor of MS.NET 
 and don't support runtime versions without a class library, but of 
 course if app.config don't forbid we can use a runtime version we 
 support instead of the specified version in assembly.
+
+------- Additional Comments From kornelpal at hotmail.com  2005-11-11 11:31 -------
+I've done some more tests and assembly version selection seems to be 
+MS.NET compatible. Only MS.NET 1.0 loaded referenced assembly 
+versions. Newer versions use their own version by default that can 
+be changed however using app.config.
+
+Runtime version selection is not MS.NET compatible, see the attached 
+test case.