[Mono-bugs] [Bug 63278][Nor] Changed - Mono 1.01 installer for Windows no longer creates registry entries

[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=63278

--- shadow/63278	2004-08-18 03:41:32.000000000 -0400
+++ shadow/63278.tmp.15528	2004-08-18 03:57:54.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 63278
 Product: Mono: Class Libraries
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: gert.driesen@pandora.be               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -39,6 +39,32 @@
 We would need to be able to determine the locations of the 1.01 and 2.01 
 releases, and NAnt users would be able to switch between these target 
 frameworks using 'mono-1.0' and 'mono-2.0' identifier (or they could set-
 up their own set of identifiers in the NAnt app config).
 
 Can we come to a solution that we can all agree on ?
+
+------- Additional Comments From gert.driesen@pandora.be  2004-08-18 03:57 -------
+Let me correct myself : I just noticed that the new installer now 
+creates registry entries in HKLM\Novell\Mono.  Is there any chance 
+this will change again in the near future, as we really need to be 
+able to rely on this.
+
+It would also be great if you could help us think about a way to 
+determine the location of the latest update for a given major 
+release.
+
+An option could be to create a separate registry value containing 
+the latest installed (bug fix) version for a given major release
+
+eg. 
+
+HKLM\Novell\Mono\CLRv1.0 (REG_SZ)  1.01
+HKLM\Novell\Mono\CLRv2.0 (REG_SZ)  2.07
+
+These values would then only be updated when installing bug fix 
+releases for a given major release.
+
+I know there's already a DefaultCLR registry value, but I don't 
+think we can use that as that value will probably be updated when a 
+new major release is installed.
+