debugging - Reasons to NOT run a business-critical C# console application via the debugger? -
i'm looking few talking points use convince coworkers it's not ok run 24/7 production application opening visual studio , running app in debug mode.
what's different running compiled console application vs. running same app in debug mode?
are there ever times when use debugger in live setting? (live: meaning connected customer facing databases)
am wrong in assuming it's bad idea run live configuration via debugger?
you suffer reduced performance when running under debugger (not mention complexity concerns mentioned bruce), , there nothing keep getting same functionality running under debugger when compiled in release mode -- can set program log unhandled exceptions , generate core dump allow debug issues after restarting app.
in addition, sounds plain wrong manually managing app needs 24/7 availability. should using scheduled tasks or sort of automated process restarting mechanism.
stepping bit, this question may provide guidance on influencing team.
Comments
Post a Comment