Rami
Rami
Hi, @gimelfarb. Thank you for ProductionStackTrace. Should I expect this PR to get merged and NuGet packages updated any time soon, or should I just deploy my own Silverlight 5...
Hi Filippo, I've fixed the build issues in https://github.com/gimelfarb/ProductionStackTrace/pull/13. I hope it helps you.
Seems pretty straight forward. https://github.com/gimelfarb/ProductionStackTrace#use-with-a-logging-framework Just add the code on the client side. Then whenever an Exception is logged in log4net, the `ProductionStackTrace` exception report will be written instead.
@erlinghaugstad created pull https://github.com/gimelfarb/ProductionStackTrace/pull/12 to fix this issue.
You have to split your log and call `ExceptionReportInterpreter.Translate` for each log entry. ExceptionReportInterpreter will stop processing when it finds the separator, `=========`.
For reference, I've submitted a feature request to allow packer to support reboots here: https://github.com/mitchellh/packer/issues/1981
Sorry I'm replying to your question late. If there are a lot of duplicate types it's less maintenance than having to specify them explicitly and/or manage them if/when they change.
I think you have to escape a forward slash with a backslash. For example `\/\/if (DEBUG`
Related: https://github.com/Huachao/vscode-restclient/issues/906
I ran into this issue on Windows 7 x64, with ansicon v1.66 installed in c:\ansicon and added to the system environment PATH variable, and running "C:\Program Files (x86)\Windows Kits\8.1\bin\x86\signtool.exe" from...