DeveloperExceptionPage does not show line numbers in stack trace

[DamianEdwards]

Using 2.0.0-preview1 bits:

• Microsoft.AspNetCore.Diagnostics 2.0.0-preview1-24820 (via Microsoft.AspNetCore.All)
• Microsoft.NETCore.App 2.0.0-preview1-002101-00

Throw a runtime exception during request processing, e.g. in an inline middleware, in a Controller action, in a Razor view/page, and the exception page displays but the stack trace contains no line numbers:

System.Exception: middleware
   at RazorPagesSample.Startup.<>c.<Configure>b__8_0(HttpContext context)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.<Invoke>d__7.MoveNext()

[DamianEdwards]

@muratg @Eilon @pranavkm @davidfowl

[NTaylorMullen]

-_- This has been regressed so many times. We seriously need to have end-to-end functional tests validating this.

[pranavkm]

Well, apparently this is a known issue: aspnet/Mvc#6120.

[NTaylorMullen]

Investigated this guy. Looks like there's a core clr issue with StackFrame that broke from netcoreapp1.1 => netcoreapp2.0. Filed an issue here.

Could use an external label 😄

[Eilon]

We can keep this issue here at least to track.

[muratg]

@Eilon we keep this in preview1 or move out? (and close if CoreCLR issue gets fixed)

[Eilon]

Can keep it here for now until we at least find out what the conclusion is on the .NET side.

[lt72]

This should now be fixed in CoreFX with dotnet/corefx#19364.

[Eilon]

@lt72 thanks!

[Eilon]

@NTaylorMullen - can you confirm we're seeing the right thing on the latest build of the CLI that I sent out?

[NTaylorMullen]

Verified by doing dotnet new -t mvc and throwing an exception in the HomeController:

All looks good!

[pranavkm]

Can you unskip aspnet/Mvc#6120?

[kichalla]

This issue resurfaced again in the mirror, probably because the corefx team merged their commits from preview1(where it regressed) to dev(where it was working when @NTaylorMullen unskipped this).

[kichalla]

This has been fixed. https://github.com/dotnet/corefx/issues/19838

[NTaylorMullen]

This has been regressed again for net461 apps. Re-opened the corefx issue: https://github.com/dotnet/corefx/issues/19838

[pranavkm]

Do we need to revive this - dotnet/extensions@31a4622?

[NTaylorMullen]

Yup, opened this issue.

To work around this issue for those watching you can add this to your csproj:

<DebugType Condition="'$(TargetFrameworkIdentifier)'=='.NETFramework'">Full</DebugType>

[NTaylorMullen]

Have other issues tracking the fix of this for net461 now:

• Exceptions thrown from Views when run from a net461 application do not contain line numbers or file info Mvc#6356
• Bring back PortablePdbReader dotnet/extensions#235