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

[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 martinf at mfconsulting.com.

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

--- shadow/63278	2004-08-28 01:25:00.000000000 -0400
+++ shadow/63278.tmp.19422	2005-06-20 17:08:34.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 63278
 Product: Mono: Runtime
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Normal
 Component: packaging
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: gert.driesen at pandora.be               
 QAContact: mono-bugs at ximian.com
@@ -65,6 +65,23 @@
 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.
 
+
+------- Additional Comments From martinf at mfconsulting.com  2005-06-20 17:08 -------
+Indeed the installer tries to stay true to Microsoft Design Guidelines
+and use the Registry keys,
+HKEY_LOCAL_MACHINE\SOFTWARE\<manufacturer>\<Product Name>\Version
+
+At the time I thought best to use Novell as the manufacturer.  In the key:
+HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Mono
+there is a DefaultCLR string value that shows the "set" Mono version.
+ There is scheme permits installing more than one version of the Mono
+Combined installer for Windows -- provided that different destination
+directories are selected when performing the installation -- and later
+using a tool like MonoLaunch
+(http://forge.novell.com/modules/xfcontent/downloads.php/monowin32/Runtime%20selector)
+the selected SDK/runtime can be changed without manually editing the
+registry.
+