.NET Tip: Debugging: Dynamically Determining the Name of the Current Function Orlando FL

Are you tired of hard-coding function names in trace messages? Have you ever used cut and paste to copy a trace statement and forgot to change the function name? There'll be no more wild goose chases because of bad function names when you determine the function name dynamically.

Local Companies

Longview Solutions Inc
407-246-1030
135 N Magnolia Ave
Orlando, FL
Perceptive Technologies
(321) 206-5999
37 N. Orange Ave. Suite 810
Orlando, FL
Aspire Solution
407-894-5560
2909 Fairgreen St
Orlando, FL
Cam Commerce Solutions
407-774-8098
4449 Lipton CT
Orlando, FL
Riptide Software
407-384-8818
3452 Lake Lynda Dr
Orlando, FL
Tapestry Solutions
407-482-0270
3361 Rouse Rd
Orlando, FL
Acusoft
407-658-9888
11869 High Tech Ave
Orlando, FL
Progressive System Solutions Inc
407-523-7676
4019 Clarcona Ocoee RD
Orlando, FL
Group One Software
407-248-0998
7380 W Sand Lake Rd
Orlando, FL
Miller Software Systems Inc
407-354-5433
8504 Cedar Cove CT
Orlando, FL

provided by: 
Originally published at Internet.com


Determining function names dynamically can simplify your debugging and trace logic as well as ensure that your trace messages match the actual code that generated them. All you have to do is wrap all your calls to Trace() with your own custom function. This utility function then can reference the stack frame to find the name of the function that called it. Here is the utility function: public static void TraceContext(string FormattedMessage) { Trace.WriteLine(string.Format(FormattedMessage, new System.Diagnostics.StackFrame(1).GetMethod().Name)); }

This function takes the message to output to Trace() and replaces the '{0}' in the message string with the name of the function that called TraceContext(). That is really all there is to it. To test the function, I created a form and added a button. In the button's click event, I call TraceContext() and call another function that also calls TraceContext(). Here is the sample code for calling TraceContext(): private void button1_Click(object sender, EventArgs e) { TraceContext("In event handler: {0}"); DynamicNameTest(); } private void DynamicNameTest() { TraceContext("In function: {0}"); }

Here is the trace output when the button is clicked: In event handler: button1_Click In function: DynamicNameTest

You now can have confidence in your trace output because you do not have any hard-coded function names in your messages.

About the Author

Jay Miller is a Software Engineer with Electronic Tracking Systems, a company dedicated to robbery prevention, apprehension, and recovery based in Carrollton, Texas. Jay has been working with .NET since the release of the first beta and is co-author of Learn Microsoft Visual Basic.Net In a Weekend. Jay can be reached via email at jmiller@sm-ets.com.

Author: Jay Miller

Read article at Internet.com site

Featured Local Company

Longview Solutions Inc

407-246-1030
135 N Magnolia Ave
Orlando, FL

Related Local Events
PERFORMANCE RACING INDUSTRY SHOW 2009
Dates: 12/10/2009 - 12/12/2009
Location: Orange County Convention Center
Orlando, FL
View Details

American Rental Association Annual Convention and Rental Trade Show
Dates: 2/8/2010 - 2/11/2010
Location: Orange County Convention Center
Orlando, FL
View Details

Pittcon - Pittsburgh Conference and Exposition on Analytical Chemistry and Applied Spectroscopy
Dates: 3/1/2010 - 3/1/2010
Location: Orange County Convention Center
Orlando, FL
View Details

OOPSLA '09: ACM SIGPLAN Object Oriented Programming Systems and Applications Conference
Dates: 10/19/2009 - 10/23/2009
Location: Disney Coronado Springs Resort
Lake Buena Vista, FL
View Details

2009 3rd International Symposium on Empirical Software Engineering and Measurement (ESEM)
Dates: 10/15/2009 - 10/16/2009
Location: Hilton Walt Disney World Resort
Lake Buena Vista, FL
View Details