[Mono-bugs] [Bug 74419][Min] New - System.IO.Directory.Exists throws exception rather than returning false
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Tue, 5 Apr 2005 14:34:37 -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 arw1961@yahoo.com.
http://bugzilla.ximian.com/show_bug.cgi?id=74419
--- shadow/74419 2005-04-05 14:34:37.000000000 -0400
+++ shadow/74419.tmp.8007 2005-04-05 14:34:37.000000000 -0400
@@ -0,0 +1,80 @@
+Bug#: 74419
+Product: Mono: Class Libraries
+Version: 1.0
+OS:
+OS Details: windows xp
+Status: NEW
+Resolution:
+Severity:
+Priority: Minor
+Component: System
+AssignedTo: mono-bugs@ximian.com
+ReportedBy: arw1961@yahoo.com
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL:
+Cc:
+Summary: System.IO.Directory.Exists throws exception rather than returning false
+
+Please fill in this template when reporting a bug, unless you know what
+you are doing.
+Description of Problem:
+
+System.IO.Directory.Exists throws exception where
+MS runtime returns false.
+
+Steps to reproduce the problem:
+
+1. compile monobug.cs (I used vs.net)
+
+using System;
+
+namespace monobug
+{
+ class Class1
+ {
+ static void Main(string[] args)
+ {
+ Console.WriteLine(""+
+ System.IO.Directory.Exists
+("http://www.example.com/index.html"));
+ }
+ }
+}
+
+2. run as a standard exe.
+3. run using mono.
+
+Actual Results:
+C:\tmp\monobug\monobug\bin\Debug>monobug.exe
+False
+
+C:\tmp\monobug\monobug\bin\Debug>mono monobug.exe
+
+Unhandled Exception: System.IO.IOException: Win32 IO returned
+ERROR_INVALID_NAME
+. Path: http://www.example.com/index.html
+in <0x00052> System.IO.Directory:Exists (string)
+in <0x00010> monobug.Class1:Main (string[])
+
+C:\tmp\monobug\monobug\bin\Debug>
+
+Expected Results:
+
+C:\tmp\monobug\monobug\bin\Debug>mono monobug.exe
+False
+
+How often does this happen?
+
+Every time.
+
+Additional Information:
+
+I got this from the 1.0.6 version. I apologize if
+it's already fixed in the development version.
+
+This was the only bug I ran into when I tried the
+test cases for the non-gui portion of xsdbXMLcs from
+http://xsdb.sourceforge.net, which was a nice surprise.
+after adding a workaround everything else seems to
+work great. Congrats!