[Mono-bugs] [Bug 53340][Wis] Changed - cannot set Environment Vars, System.Collections.Specialized.StringDictionary incomplete?

[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 lluis@ximian.com.

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

--- shadow/53340	2004-01-26 12:48:51.000000000 -0500
+++ shadow/53340.tmp.27830	2004-03-29 15:02:12.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 53340
-Product: Mono/Class Libraries
+Product: Mono: Class Libraries
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
-Status: NEW   
-Resolution: 
-Severity: 
+Status: RESOLVED   
+Resolution: FIXED
+Severity: Unknown
 Priority: Wishlist
 Component: System
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: eb@zombie.inka.de               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -43,6 +43,33 @@
 
 I assume that the class System.Collections.Specialized.StringDictionary
 (the one which contains the environment strings) is not complete.
 
 Thanks,
 Eduard.
+
+------- Additional Comments From lluis@ximian.com  2004-03-29 15:02 -------
+Ok, several things:
+
+1) This is already fixed in CVS. Environment variables are correctly
+assigned in the new process.
+
+2) The test case is wrong, it should not compile because Start(string)
+is a static method and you can't call a static method using an
+instance reference. It compiles because of an MCS bug (reported now as
+#56174).
+
+3) This is the fixed test case:
+
+using System;
+using System.Diagnostics;
+
+class TestIt {
+  public static void Main() {
+    Process p = new Process();
+    p.StartInfo.EnvironmentVariables.Add("foo", "bar");
+    p.StartInfo.FileName = "xterm";
+    p.StartInfo.UseShellExecute = false;
+    p.Start();
+  }
+}
+