-
Notifications
You must be signed in to change notification settings - Fork 108
Exceptions during razor views rendering don't show the source line #293
Comments
Seems like an issue with compiling using the |
The issue's been fixed for RTM - https://github.com/dotnet/coreclr/issues/3906. We're working on picking up the packages now so this is likely to get fixed soon. I filed aspnet/Mvc#4737 to add a functional test to verify this behavior is covered. |
The RC3 packages fix this issue in netcoreapp, but it's broken on desktop. I guess we could generate full pdbs if the right components are present. @davidfowl, does that sound ok? |
Add a test to verify exceptions thrown from views is pretty printed by diagnostics middleware Fixes aspnet/Diagnostics#293 Fixes #4737
Add a test to verify exceptions thrown from views is pretty printed by diagnostics middleware Fixes aspnet/Diagnostics#293 Fixes #4737
Add a test to verify exceptions thrown from views is pretty printed by diagnostics middleware Fixes aspnet/Diagnostics#293 Fixes #4737
@pranavkm why is dotnet/coreclr#3906 considered closed if the problem is only fixed when using .NET core? Have you filed a CoreFx bug for full desktop support? |
Add a test to verify exceptions thrown from views is pretty printed by diagnostics middleware Fixes aspnet/Diagnostics#293 Fixes #4737
@davidfowl's going to commonize the pdb reader (#300) and use it in Hosting and Diagnostics. I'll check in the test part of aspnet/Mvc@73ddec7 once this is done to get some e2e coverage. |
Add a test to verify exceptions thrown from views is pretty printed by diagnostics middleware Fixes aspnet/Diagnostics#293 Fixes #4737
Can repro in a new WebApp from template.
Repro:
Index.cshtml
with@(((string)null).ToString()
Result:
Expected:
It should display the line number where the exception occurred.
NB:
sourceTree
value the line numbers are generated in the razor source.The text was updated successfully, but these errors were encountered: