[Mono-bugs] [Bug 79797][Min] Changed - [PATCH] create monow.exe on Windows

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Nov 1 07:21:20 EST 2006

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 kornelpal at gmail.com.


--- shadow/79797	2006-11-01 06:38:12.000000000 -0500
+++ shadow/79797.tmp.29742	2006-11-01 07:21:20.000000000 -0500
@@ -56,6 +56,24 @@
 "mono --debug" was called. W/out this conditional one has to
 recompile with /target:exe to see what's going on...
 MS.NET didn't had to solve any problems, because it doesn't
 have a "driver" like mono.exe.
+------- Additional Comments From kornelpal at gmail.com  2006-11-01 07:21 -------
+Just for the clarity: I agree that crating a monow.exe is good and 
+is required. So I support that patch.
+The problem I was talking about is that MS runtime prints the stack 
+trace to console as well. And /target:winexe applications have no 
+console. Currently this is the same for Mono. The only difference is 
+that a console window is "flickering" that is caused by the desing 
+of Windows and I personally consider that design to be poor. And 
+this is what you path works around.
+And now I agree that --debug is used for debugging so users would 
+like to see stack trace. The stack trace could be displayed by 
+System.Windows.Forms just like MS.NET does but that involves MWF as 
+well so I support the second patch as well. And if there will be 
+other solution in the future this second patch can be undone easily 
+if required.

More information about the mono-bugs mailing list