You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Source code location isn't embedded directly in .net binaries, but is stored separately in .pdb files. There is some infrastructure in the runtime to locate and extract the relevant data, but it can turn out to be quite difficult to use; the instrumentation method itself can't use managed code reliably, and these routines are managed. For this reason this task can turn out to be more complicated than it can be expected.
The text was updated successfully, but these errors were encountered:
Inside of an IDE environment, it may not be necessary to know the source
code location in order to open the code. Class name and method name may be
enough to find the right source.
On Fri, Feb 12, 2021 at 8:24 AM Rafał Rzepecki ***@***.***> wrote:
Source code location isn't embedded directly in .net binaries, but is
stored separately in .pdb files. There is some infrastructure in the
runtime to locate and extract the relevant data, but it can turn out to be
quite difficult to use; the instrumentation method itself can't use managed
code reliably, and these routines are managed. For this reason this task
can turn out to be more complicated than it can be expected.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#12>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAVC63M7MEWH7XSXUOHJALS6UTZFANCNFSM4XQV2NQA>
.
Source code location isn't embedded directly in .net binaries, but is stored separately in .pdb files. There is some infrastructure in the runtime to locate and extract the relevant data, but it can turn out to be quite difficult to use; the instrumentation method itself can't use managed code reliably, and these routines are managed. For this reason this task can turn out to be more complicated than it can be expected.
The text was updated successfully, but these errors were encountered: