[Mono-bugs] [Bug 80640][Maj] New - Mono Differences to Microsoft runtime

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Jan 26 16:46:44 EST 2007


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 jeffr at newhartsystems.com.

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

--- shadow/80640	2007-01-26 16:46:44.000000000 -0500
+++ shadow/80640.tmp.27766	2007-01-26 16:46:44.000000000 -0500
@@ -0,0 +1,46 @@
+Bug#: 80640
+Product: Mono: Runtime
+Version: 1.2
+OS: 
+OS Details: Windows XP Pro
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: interop
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: jeffr at newhartsystems.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Mono Differences to Microsoft runtime
+
+I am trying to make our application run under Mono.  It consists of over 
+20 dll's and 4 exe's.  Here are some of the things I have noticed when I 
+try to run under mono that do not happen under the Microsoft runtime:
+
+1. When I try to set the .Image property in a ToolStripButton or MenuItem 
+the error "Unknown Exception" is thrown.  None of my tool bars work 
+because I can't set the Image property.
+
+2.When I set ToolStripButton.Text to null I get an exception thrown under 
+Mono and not under Microsoft runtime.
+
+3. System.Reflection.Assembly.GetExecutingAssembly().GetName().CodeBase 
+returns a string in uri format with %20's for spaces and MS returns 
+spaces (unless launched over http Clickonce)
+
+4.Common Dialog Box SaveFileDialog 
+	Setting FilterIndex to an invalid index causes an exception after 
+the dialog is closed
+
+5.A System.Windows.Form which has MinimizeBox, MaximizeBox, and 
+ControlBox set to false and the Text property set to null does not hide 
+the titlebar in Mono.
+
+6.Setting a System.Windows.Form.Text to null throws an exception
+
+7.Changing System.Windows.Forms.MinimizeBox or 
+System.Windows.Forms.MaximizeBox after window is displayed causes 
+application to terminate without throwing an exception.


More information about the mono-bugs mailing list