ExecutingAssembly context while debugging managed code

I was recently debugging an issue with a computed path in managed code, The goal is to find a file in the path relative to the currently executing assembly. Every time i was debugging the issue and i inspect the Assembly.GetExecutingAssembly() when the first chance exception is caught in visual studio, and i find that the path is mscorlib.dll and not my executing assembly. For a minute i was confused and then i realized that the exception had went out of scope and the runtime had handled the exception and Assembly.GetExecutingAssembly() returns the assembly whose code is currently executing. Code means the JIT'ed code actually.