[Mono-bugs] [Bug 45585][Wis] New - Mono 0.25 Windows Installer

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
Sat, 28 Jun 2003 14:53:35 -0400 (EDT)


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 spouliot@videotron.ca.

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

--- shadow/45585	Sat Jun 28 14:53:35 2003
+++ shadow/45585.tmp.28192	Sat Jun 28 14:53:35 2003
@@ -0,0 +1,62 @@
+Bug#: 45585
+Product: Mono/Runtime
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: spouliot@videotron.ca               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Mono 0.25 Windows Installer
+
+1.	The installer didn't ask where to install the files (e.g. I wanted 
+mono on my C drive, like I did for previous release, but it got installed 
+on my D drive, where my W2K OS is installed).
+
+2.	Missing assemblies (\lib)
+- Mono.Security.dll
+- Mono.Security.Win32.dll
+
+3.	Missing tools (\bin)
+- cert2spc.exe (however cert2spc.exe.sh is present)
+- makecert.exe
+- sn.exe
+
+* note: all three tools depends on missing assembly Mono.Security.dll
+
+
+4.	Update machine.config to include
+
+	<mscorlib>
+		<cryptographySettings>
+			<cryptoNameMapping>
+				<cryptoClasses>
+					<cryptoClass 
+CapiRNG="Mono.Security.Cryptography.RNGCryptoServiceProvider, 
+Mono.Security.Win32, Version=0.0.0.0, Culture=neutral, 
+PublicKeyToken=null"/>
+				</cryptoClasses>
+				<nameEntry name="RandomNumberGenerator" 
+class="CapiRNG" />
+				<nameEntry 
+name="System.Security.Cryptography.RandomNumberGenerator" 
+class="CapiRNG" />
+				<nameEntry 
+name="System.Security.Cryptography.RNGCryptoServiceProvider" 
+class="CapiRNG"/>
+			</cryptoNameMapping>
+		</cryptographySettings>
+	</mscorlib>
+
+inside <configuration></configuration> or else everything depending on RNG 
+(most of crypto) will fail.
+
+* note: this configuration addition requires the missing assembly 
+Mono.Security.Win32.dll