{"id":65656,"date":"2021-07-10T04:10:06","date_gmt":"2021-07-10T08:10:06","guid":{"rendered":"http:\/\/bangla.salearningschool.com\/recent-posts\/debug-and-trace-classes-in-net-misc-net\/"},"modified":"2021-07-10T04:10:06","modified_gmt":"2021-07-10T08:10:06","slug":"debug-and-trace-classes-in-net-misc-net","status":"publish","type":"post","link":"http:\/\/bangla.sitestree.com\/?p=65656","title":{"rendered":"Debug and Trace classes in .Net #Misc .Net"},"content":{"rendered":"

Brought from our old-site (yes, pretty old short-note): http:\/\/salearningschool.com\/displayArticle.php?table=Articles&articleID=636&title=Debug%20and%20Trace%20Classes%20in%20.Net<\/p>\n

Debug and Trace classes in .Net<\/b><\/p>\n

You can always debug your applications line by line. However, when the applications get very bigger\/larger, debugging line by line may not be an efficient way for finding errors in code (well, you can first find out the error region and then can debug line by line). Debug and Trace classes are handy in such cases. Using Debug and Trace classes, you can find errors and write them in a file or create an event log. Later, you can check the file or the event log to see what kinds of errors the applications are causing. They both provide the same functionalities except that Debug class works only in the debug mode. Trace can work even after the applications are released and also you can control the error reporting from released versions. In a .config file you can change the behavior of the Trace class.<\/p>\n

Logging Trace Output into a text file<\/b><\/p>\n