我的店维持一个相当新的应用程序工作。该应用程序仍然有其公平份额的错误，与众多的门票即将在日常。我们正在与那些票给出的错误信息是不是有用，因为它可能是因为应用程序在发布模式，这是我读的体积更小，速度更快（很有意义）编制。

I work for a shop that maintains a fairly new app. The app still has its fair share of bugs, with numerous tickets coming in daily. The error information we're given with those tickets is not as useful as it might be because the application was compiled in Release mode, which I read is smaller and faster (makes sense).

有什么后果来部署.NET应用程序到生产这是在调试模式下编译？我希望这将是一个有点慢，但我读过的区别是名义上的。这就向我们保证，当我们在门票上的错误，我们与这些错误相关的行数和这当然，使调试变得更加容易。

Are there any ramifications to deploying a .NET application to production that was compiled in Debug mode? I would expect it would be a bit slower, but I've read the difference is nominal. This would assure us that when we get errors on tickets we have line number associated with those errors and this, of course, makes debugging much easier.

任何重大的红旗，将prevent你这样做呢？我负责研究的可能性。因此，感谢您的反馈意见。

Any major red flags that would prevent you from doing this? I'm tasked with researching the possibility. So thanks for any feedback.

推荐答案

部署您的应用程序的调试，而不是释放模式会降低性能。当然妥协可。我建议下列之一：

Deploying your app in DEBUG instead of Release mode will slow down your performance. Of course compromises can be made. I would suggest one of the following:

看看添加一个全球性的错误处理到的OnError在你的Global.asax - 在看类似的妥协来这的那么建议由Scott Hanselman的 Look at adding a global error handler to the OnError in your global.asax- Look at a compromise similar to this one suggest by Scott Hanselman