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 [EMAIL PROTECTED]

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

--- shadow/81051        2007-03-06 12:04:18.000000000 -0500
+++ shadow/81051.tmp.22720      2007-03-06 12:04:18.000000000 -0500
@@ -0,0 +1,31 @@
+Bug#: 81051
+Product: Mono: Runtime
+Version: 1.0
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: debug
+AssignedTo: [EMAIL PROTECTED]                            
+ReportedBy: [EMAIL PROTECTED]               
+QAContact: [EMAIL PROTECTED]
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: When running with --debug, we should activate all debug features 
automatically
+
+Capturing miguel's thoughts from an irc discussion:
+
+<miguel_> But I have been thinking that when the runtime runs with --debug
+<miguel_> We should set an AppDomain flag
+<miguel_> So that all "debug" features are turned on automatically
+<miguel_> Instead of having to turn on 10 different debug features everywhere
+<miguel_> (This was in the context of ASP.NET that needs mcs to be called
+with debug, pages to be compiled with debug, children to be called with
+debug, etc)
+<miguel_> Debugging an ASP.NET app means 'turning on debug' in 4-5 places today
+<grendel> yep
+<miguel_> It is as bad as our "debug shared library problems" which usually
+means using 2 environment variables that nobody remembers
_______________________________________________
mono-bugs maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-bugs

Reply via email to