-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Razor diagnostic experience when not using a debugger #561
Conversation
Improve the experience of Razor view template exceptions by including the error messages in the output. When running outside of a debugger, this information is otherwise nearly impossible to retrieve.
I finally got annoyed enough with having to load up a debugger and break on exceptions just to see the razor syntax I screwed up 👍 |
Improve Razor diagnostic experience when not using a debugger
ok brilliant, thx! |
Great, frustration-driven-development is a great way to encourage pull-requests! :) |
At the rate I'm going, I might submit the Razor v2 integration soon enough!! ;) |
Thanks Aaron - this is going to be quite helpful |
Agreed. This is fantastic. I was contemplating doing the same thing, but I just hadn't gotten fed up enough yet. 👍 |
@aaronlerch Great, if you do want to take on Razor v2 you should talk with @dsimunic as you might be able to divvy up the work: https://github.com/ServiceStack/ServiceStack/issues/547 |
I still like ASP.NET's ability to show the source in the browser when debugging. @mythz Would you accept a pull request that had the same kind of dev experience? I'd be happy to write a pull request. |
@bchavez yep for sure, thing to watch out for is |
Is this change now released in v3.9.45+ as I'm still getting a generic HttpCompileException for binding errors? |
Since this change is from a month ago - there have been several releases to NuGet since then, so yes, I would say it is released. Post a question on stackoverflow or submit a broken test case here. |
Razor support got rewritten since this commit. I committed one improvement to the latest Razor code yesterday (#684), please see if that resolves your problem. On 21 mai 2013, at 13:53, waynebrantley notifications@github.com wrote:
|
Improve the experience of Razor view template exceptions by including
the error messages in the output. When running outside of a debugger,
this information is otherwise nearly impossible to retrieve.
An example output (this happens to be running under Mono on a mac):