Tip #83: Did you know... You can get the name of the calling method from the stack using reflection?http://blogs.msdn.com/webdevelopertips/archive/2009/06/23/tip-83-did-you-know-you-can-get-the-name-of-the-calling-method-from-the-stack-using-reflection.aspxNearly every program needs a logger to log events, errors and exceptions. Sometimes it is also useful to log the name of the method that logged the event. The easiest way to do that is to make the log method take both the calling method name and eventen-USCommunityServer 2.1 SP1 (Build: 61025.2)re: Tip #83: Did you know... You can get the name of the calling method from the stack using reflection?http://blogs.msdn.com/webdevelopertips/archive/2009/06/23/tip-83-did-you-know-you-can-get-the-name-of-the-calling-method-from-the-stack-using-reflection.aspx#9801326Wed, 24 Jun 2009 14:28:27 GMT91d46819-8472-40ad-a661-2c78acb4018c:9801326Marijn<p>Indeed, StackTrace.GetFrame.GetMethod is nice for tose things.</p> <p>However, beware that an optimizing compiler might optimize away stackframes (due to inlining for example). In .NET you can add a JIT attribute ([Runtime.CompilerServices.MethodImpl(Runtime.CompilerServices.MethodImplOptions.NoInlining)]) but that only instructs the JIT to not inline. The C# compiler can not be told to not inline (but it does not seem to inline currently).</p> re: Tip #83: Did you know... You can get the name of the calling method from the stack using reflection?http://blogs.msdn.com/webdevelopertips/archive/2009/06/23/tip-83-did-you-know-you-can-get-the-name-of-the-calling-method-from-the-stack-using-reflection.aspx#9801516Wed, 24 Jun 2009 17:03:40 GMT91d46819-8472-40ad-a661-2c78acb4018c:9801516Aaron<p>You beat me to this comment. I had this experience but I tried to used for something else than just logging and ended up being a nasty bug only present when compiled on release mode, so be cautious when using it as your code might be optimized by the compiler.</p> Good for debugging http://blogs.msdn.com/webdevelopertips/archive/2009/06/23/tip-83-did-you-know-you-can-get-the-name-of-the-calling-method-from-the-stack-using-reflection.aspx#9801611Wed, 24 Jun 2009 18:02:57 GMT91d46819-8472-40ad-a661-2c78acb4018c:9801611Greg<p>I've used this for debugging/logging but avoided it for non-debug code. &nbsp;</p> <p>It still doesn't beat printable to end user message numbers in error/log messages as you can text search for them right away to get the source line that printed the message.</p> re: Tip #83: Did you know... You can get the name of the calling method from the stack using reflection?http://blogs.msdn.com/webdevelopertips/archive/2009/06/23/tip-83-did-you-know-you-can-get-the-name-of-the-calling-method-from-the-stack-using-reflection.aspx#9801758Wed, 24 Jun 2009 20:05:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:9801758Casey Barton<p>I just instinctively reference log4net, even for simple little on-off tools. You can log calling method amongst a hundred other attributes, just by configuring a format string.</p> re: Tip #83: Did you know... You can get the name of the calling method from the stack using reflection?http://blogs.msdn.com/webdevelopertips/archive/2009/06/23/tip-83-did-you-know-you-can-get-the-name-of-the-calling-method-from-the-stack-using-reflection.aspx#9803466Thu, 25 Jun 2009 15:26:44 GMT91d46819-8472-40ad-a661-2c78acb4018c:9803466Óscar González<p>How can you get the called method from the constructor?</p> re: Tip #83: Did you know... You can get the name of the calling method from the stack using reflection?http://blogs.msdn.com/webdevelopertips/archive/2009/06/23/tip-83-did-you-know-you-can-get-the-name-of-the-calling-method-from-the-stack-using-reflection.aspx#9806049Sat, 27 Jun 2009 01:27:09 GMT91d46819-8472-40ad-a661-2c78acb4018c:9806049Nicholas Piasecki<p>Referencing Aaron and Marijn, I got burned by this too. It's prone to error and I recommend not using it, unless you're positive it will only run in Debug builds.</p>