Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Im a little confused over how to use the .NET Trace and Debug classes.
Why would you bother using Trace instead of Debug?
Trace.TraceError() Trace.TraceInformation() Trace.Assert() Debug.WriteLine() Debug.Assert() Also, I understand that Debug statements are ignored when your in Release config mode, but If trace statements apply all the time, how does this affect performance?
At the simplest level, they have different compilation switches – i.e.
Debug.WriteLineetc is only toggled if you have theDEBUGcompilation symbol (not common for release builds), where-asTrace.WriteLinewill usually be included even in release builds.The
Traceroute has customizable trace-listeners, that can be plumbed in via configuration;Debuggenerally goes to a debugger as the listener. Of course, there are 3rd-party trace systems that offer much more flexibility.