Argh! Evil!

Don't even bother to try.
If someone wants to debug the application, they will strip it away, or tell the debugger to ignore those options.
You will end up with undebugable code, and let me tell you, printf is _NOT_ a fine way to work.

I think that everything within the System.Diagnostics.Debuc namespace get stripped whenever you compile an app without debug information.

In theory, one could use the DebuggerStepThrough attribute to make sure that the code within a method is non-debuggable. I haven't tried it, as I don't need that kind of functionality in my current job.

There are some things.
when you have plenty dll's from your company in your project, you dont want to debug them all. so the most of these have the step thru option, so it dont even stop there when theres an ecxeption. it stops in your code (thinking of, that you passed a wrong parameter or so. if its in the dll the error, you can just pass another dll without that option in). and the other thing i use sometimes is Debug.Assert. i pointed out an possible usage of that in my "Get the size of the Viewstate" article. www.code4ward.net/.../posteditor.aspx" rel="nofollow">www.code4ward.net/.../posteditor.aspx">www.code4ward.net/.../posteditor.aspx" rel="nofollow">www.code4ward.net/.../posteditor.aspx
so, you want to have an warning dialog when something happens. also ms use that often. e.g. when you create an db scheme from vs, the code it produce is with step Thru