[Mono-bugs] [Bug 53260][Nor] Changed - System.Environment.GetFolderPath Throws Exceptions
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Tue, 10 Feb 2004 08:42:53 -0500 (EST)
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=53260
--- shadow/53260 2004-01-23 13:27:45.000000000 -0500
+++ shadow/53260.tmp.9780 2004-02-10 08:42:53.000000000 -0500
@@ -1,10 +1,10 @@
Bug#: 53260
Product: Mono/Class Libraries
Version: unspecified
-OS:
+OS: unknown
OS Details: Microsoft Windows Server 2003 Enterprise Edition
Status: NEW
Resolution:
Severity: Unknown
Priority: Normal
Component: CORLIB
@@ -12,12 +12,13 @@
ReportedBy: jconley@winfessor.com
QAContact: mono-bugs@ximian.com
TargetMilestone: ---
URL:
Cc:
Summary: System.Environment.GetFolderPath Throws Exceptions
+BugsThisDependsOn: 50532
Description of Problem:
The System.Environment.GetFolderPath() method throws
ArgumentNullExceptions in Windows. GetFolderPath is very useful for
finding places to put temporary files.
@@ -92,6 +93,15 @@
How often does this happen?
Every Time
Additional Information:
This seems to work just fine on Linux. Paths that do not exist on that
platform simply return an empty string.
+
+------- Additional Comments From spouliot@videotron.ca 2004-02-10 08:42 -------
+The ArgumentNullException is due to the fact that the HOME environment
+variable isn't defined under Windows by default (except in cygwin).
+
+Path.Combine throw the exception because it receive a null parameter
+(which is normal).
+
+This is detailled in #50532 with a proposed patch.