[Mono-bugs] [Bug 77365][Nor] Changed - Application crash at start!

[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 mkestner at ximian.com.

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

--- shadow/77365	2006-01-26 08:36:26.000000000 -0500
+++ shadow/77365.tmp.28490	2006-03-27 13:37:56.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 77365
 Product: gtk#
 Version: unspecified
 OS: unknown
 OS Details: Red Hat Enterprise Linux 4 Desktop, Gnome, ugly as sin!
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: NOTABUG
 Severity: Unknown
 Priority: Normal
 Component: general
 AssignedTo: lupus at ximian.com                            
 ReportedBy: PauloMorfeo at Portugalmail.pt               
 QAContact: mono-bugs at ximian.com
@@ -235,6 +235,16 @@
 	/usr/bin/mono(sinh+0x41) [0x805c171]
 
 #####
 
 ------- Additional Comments From vargaz at gmail.com  2006-01-26 08:36 -------
 -> gtk#
+
+------- Additional Comments From mkestner at ximian.com  2006-03-27 13:37 -------
+This isn't a bug.  The reason for your failure is that the field
+initializations are occuring prior to your constructor body execution,
+where the Application.Init() call resides.
+
+The obvious solution is to move the Application.Init call to the Main
+method.  If you wanted to avoid the Gtk reference in that file, you
+could call Application.Init from a static ctor on the Janela class as
+well and still be able to use field initializers.