[Mono-bugs] [Bug 76795][Maj] New - Visual Basic 2005 Forms do not work

[bugzilla-daemon at 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 dontwantspam1 at earthlink.net.

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

--- shadow/76795	2005-11-22 23:11:17.000000000 -0500
+++ shadow/76795.tmp.13152	2005-11-22 23:11:17.000000000 -0500
@@ -0,0 +1,93 @@
+Bug#: 76795
+Product: Mono: Runtime
+Version: 1.1
+OS: other
+OS Details: Fedora Core 3
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: JIT
+AssignedTo: lupus at ximian.com                            
+ReportedBy: dontwantspam1 at earthlink.net               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Visual Basic 2005 Forms do not work
+
+Description of Problem:
+Using the latest stable version of Mono (1.1.10-2) on Fedora Core 3, 
+Microsoft Visual Basic 2005 (Express Edition) forms do not run as is.
+
+Steps to reproduce the problem:
+1. Start a new project in Microsoft Visual Basic 2005 Express Edition.  
+You should get a blank form.
+2. Change the build to a release build
+3. Build the project
+4. Transfer the .exe file to a Fedora Core 3 x86
+5. Open a terminal window and type "mono whateveritis.exe"
+
+Actual Results:
+I get the following error:
+
+** ERROR **: file class.c: line 2418 (mono_class_setup_parent): should 
+not be reached
+aborting...
+Aborted
+
+
+Expected Results:
+This should, if it were running correctly, pop up a blank window on the 
+screen.
+
+
+How often does this happen? 
+Every time I've tried this.  It's pretty important, since form designing 
+is a main part of designing programs in Visual Basic on Windows.  I've 
+tried this with about every option combination I thought might help - 
+same thing every time.
+
+
+Additional Information:
+I have been able to write programs that work on Mono using Visual Basic 
+2005 Express Edition - just not with forms designed visually.  The only 
+way I've been able to get anything to work is to use Sub Main as the 
+startup object.  Then, you can write code like the following code, which 
+does run on Mono on FC3:
+
+Module Module1
+    Sub main()
+        Dim x as System.Windows.Forms.ColorDialog
+        
+        x.ShowDialog()
+    End Sub
+End Module
+
+In fact, you can also do code like this:
+
+Module Module1
+    Sub main()
+        Dim x as System.Windows.Forms.ColorDialog
+        Dim y as New System.Windows.Forms.Form
+        
+        x.ShowDialog()
+        y.Text = "Test"
+        y.BackColor = x.Color
+        y.ShowDialog()
+    End Sub
+End Module
+
+This code also works properly.  Here's some code that doesn't:
+
+Module Module1
+    Sub main()
+        Form1.ShowDialog()
+    End Sub
+End Module
+
+This code gives precisely the same error as is listed above.  So, VB 
+forms do in fact work if they're coded explicitly, but not like they 
+should.  It pretty much entirely defeats the purpose of using VB.  Sorry 
+if this is the wrong place for this.  It's my first Bugzilla submission.  
+Don't know if the component is right either - not a clue on that one!