Customizing the behavior of System.Diagnostics.Debug.Assert [Matt Ellis]

re: Customizing the behavior of System.Diagnostics.Debug.Assert [Matt Ellis]

Ran Davidovitz — Thu, 19 Jul 2007 21:50:10 GMT

Hi,

It’s very interesting that I been working on that same issue couple of days ago.

I have two questions:

1. I don’t understand why AssertUiEnabled is default to TRUE in ASP.NET application?

2. Other issue that troubles me is I don’t understand why is the Configuration section classes of all the diagnostics section are internal? (E.g. I wanted to do a simple program that updates the configuration and I had to create wrapper class for the configuration sections and not use the already written classes of .net)?

Thanks

re: Customizing the behavior of System.Diagnostics.Debug.Assert [Matt Ellis]

Jonathan Edwards — Fri, 20 Jul 2007 05:04:36 GMT

I find Debug.Assert frustrating because it does not do what I want: when running under the debugger, pop straight into the debugger. The dialog is an annoying waste of time. I have written my own Assert that just throws an exception, but it is missing one piece of magic from Debug.Assert:

How does Debug.Assert keep its own stack frames off the top of the stack? When you click through the dialog the debugger shows the top stack frame from your app, not the Debug class. Is this an undocumented .NET feature?

re: Customizing the behavior of System.Diagnostics.Debug.Assert [Matt Ellis]

Matt Ellis — Sat, 21 Jul 2007 02:05:03 GMT

@Jonathan Edwards,

By default Visual Studio won't attempt to step into framework code since you likely don't have symbols or sources for it. This is similar to if your code call some framework API that throws an exception, Visual Studio show break into the debugger at the point where your code called the offending method, not within the framework code.

I think that if you apply System.Diagnostics.DebuggerNonUserCodeAttributeto your new Assert method that Visual Studio will prevent it from being shown on the call stack.

Hope this helps!

Cheers,

Matt

re: Customizing the behavior of System.Diagnostics.Debug.Assert [Matt Ellis]

Paulo Morgado — Tue, 31 Jul 2007 20:48:49 GMT

I've been setting /configuration/sytem.diagnostics/assert/@assertuienabled to "false" on all my unit testing and ASP.NET applications and it has worked fine, so far.