http://bugzilla.novell.com/show_bug.cgi?id=552658

http://bugzilla.novell.com/show_bug.cgi?id=552658#c2


--- Comment #2 from Brian Kesecker <[email protected]> 2010-01-21 
16:55:00 UTC ---
Ok, got to the point in my project where this little problem matters.  So, I
through together an Excel spreadsheet with a few case studies of Windows
behavior versus Linux behavior.

However, in 2.6.x, the code in my second comment no longer works.

In fact, there are a few instances where the interface can be crashed by
permutating the values.  I cover these in the Excel file.

Finally, I took a few screen captures of error messages just so the progress
can be captured.

In test case 1 for Linux, I get the following exception in the Output window:

System.ArgumentException: Directory does not exists
Parameter name: value
  at System.IO.FileSystemWatcher.set_Path (System.String value) [0x0007c] in
/usr/src/packages/BUILD/mono-2.6.1/mcs/class/System/System.IO/FileSystemWatcher.cs:325
 
  at (wrapper remoting-invoke-with-check) System.IO.FileSystemWatcher:set_Path
(string)
  at EdgeFrontierEngine.Main.Main_Load (System.Object sender, System.EventArgs
e) [0x00471] in EdgeFrontierManager/Main.vb:141 
  at System.Windows.Forms.Form.OnLoad (System.EventArgs e) [0x00022] in
/usr/src/packages/BUILD/mono-2.6.1/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:2162
 
  at System.Windows.Forms.Form.OnLoadInternal (System.EventArgs e) [0x00029] in
/usr/src/packages/BUILD/mono-2.6.1/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:2988
 

The related screenshot error message is attached, as well as other
miscellaneous errors that occurred while performing these tests (useful or
not).

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
_______________________________________________
mono-bugs maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-bugs

Reply via email to