There is also a fundamental difference in thinking when we want to use trace and when want to debug. Tracing is a process about getting information regarding program's execution. On the other hand debugging is about finding errors in the code.
Debug and trace enables you to monitor the application for errors and exception without VS. NET IDE.
In Debug mode compiler inserts some debugging code inside the executable. As the debugging code is the part of the executable they run on the same thread where the code runs and they do not given you the exact efficiency of the code ( as they run on the same thread). So for every full executable DLL you will see a debug file also as shown in figure ‘Debug Mode’.
See the following video for how to Skip debugging in ASP. NET: -
Click for more ASP. NET Interview questions
Regards,
Visit for more authors’ blog on ASP. NET Interview questions
Debug and trace enables you to monitor the application for errors and exception without VS. NET IDE.
In Debug mode compiler inserts some debugging code inside the executable. As the debugging code is the part of the executable they run on the same thread where the code runs and they do not given you the exact efficiency of the code ( as they run on the same thread). So for every full executable DLL you will see a debug file also as shown in figure ‘Debug Mode’.
Figure: - Debug mode
Trace works in both debug as well as release mode. The main advantage of using trace over debug is to do performance analysis which cannot be done by debug. Trace runs on a different thread thus it does not impact the main code thread.See the following video for how to Skip debugging in ASP. NET: -
Click for more ASP. NET Interview questions
Regards,
Visit for more authors’ blog on ASP. NET Interview questions
No comments:
Post a Comment