@blowdart:
You can get a runtime stack under three conditions, the DLLs are debug compiled, you have debug turned on in the web.config and you disable the custom error page, use the default and set it to show to all IPs (or local, and RDP to the web server and load the page)
The default solution for .NET web apps is to show the stack trace to HTTP clients in the browser?
Even PHP logs errors in /var/log
Why does a server even need to be running a display manager anyway? Why would you RDP to a production server and start surfing the web?
This seems extremely backwards.
Lets say for an instant that this is a very high traffic website where if you enable a debug build it will slow it down enough to cause a problem and if you show stack traces in the browser people will get scared just like they did on MySpace and never come back.
What now? Can't I just silently log errors to a log file without using another library?
Is there an equivalent of catalina.out or not?
