[Mono-bugs] [Bug 76636][Nor] Changed - Runtime and assembly 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-05 10:26:35.000000000 -0500
+++ shadow/76636.tmp.19168	2005-11-07 07:14:39.000000000 -0500
@@ -78,6 +78,26 @@
 ------- Additional Comments From kornelpal at hotmail.com  2005-11-05 10:26 -------
 As we haven't got a version 1.0 class library I think v1.0.3705 
 should be removed from supported_runtimes as we don't support 
 v1.0.3705 in fact but we execute v1.0.3705 images using runtime 1.1 
 similar to default MS.NET behavior when there is not MS.NET 1.0 
 installed but there is MS.NET 1.1 installed.
+
+------- Additional Comments From kornelpal at hotmail.com  2005-11-07 07:14 -------
+Mono runtime has formal support for runtime versions v1.0.3705 and 
+v2.0.50215 but haven't got class libraries for these versions. We 
+only have class library for v1.1.4322 and v2.0.50727.
+
+The result is that v1.0.3705 and v2.0.50215 are supported but 
+Environment.Version is constant instead of an internal call, so 
+invalid runtime version is returned. The more wird thing is that 
+altough the application see that it is running on v1.1.4322 or 
+v2.0.50727 because of Environment.Version and appropriate 
+mscorlib.dll version, the runtime emits runtime version to 
+assemblies based on it's internal version number 
+(mono_get_runtime_info ()->runtime_version) that is not exposed to 
+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.