[Mono-bugs] [Bug 62913][Nor] New - Mono does not fall back to 1.0 profile (1.1 runtime) when 2.0 profile is not available

[bugzilla-daemon@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 gert.driesen@pandora.be.

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

--- shadow/62913	2004-08-12 05:33:02.000000000 -0400
+++ shadow/62913.tmp.7158	2004-08-12 05:33:02.000000000 -0400
@@ -0,0 +1,33 @@
+Bug#: 62913
+Product: Mono: Runtime
+Version: unspecified
+OS: GNU/Linux [Other]
+OS Details: Gentoo 2.6.7 r13
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: gert.driesen@pandora.be               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Mono does not fall back to 1.0 profile (1.1 runtime) when 2.0 profile is not available
+
+Apparently Mono does not seem to fallback to the 1.0 profile (1.1 
+runtime) when the 2.0 profile is not available.
+
+I have attached an assembly built using .NET 1.0, and with the following 
+<startup> section in the application configuration file :
+
+        <supportedRuntime version="v2.0.40607" />
+        <supportedRuntime version="v1.1.4322" />
+        <supportedRuntime version="v1.0.3705" />
+
+So, Mono does first determine if the 2.0 runtime/profile is available and 
+fallback to the next supported runtime.  In case of Mono there's no 
+seperate runtime (yet), but it could check if the 2.0 mscorlib is 
+available (and in sync with the runtime). And if not, fallback to using 
+the 1.1 runtime (in this case).