ASP.NET网站DLL：Debug vs. Release version [英] ASP.NET Website DLL: Debug vs. Release version

问题描述

将ASP.NET Web应用程序.dll文件上传到我的网站的/ bin /目录中时，使用调试版本与重新编译发行版本有任何不利之处。

When uploading my ASP.NET web application .dll file to my website's /bin/ directory, are there any disadvantages to using the debug version as opposed to recompiling a release build.

例如，在网站上本地工作时，构建配置设置为Debug。当事情看起来不错，我会继续上传最新的.dll网站/ webapp。我应该在这个时候把build配置改成Release，然后编译，然后将该版本的.dll上传到服务器上？

For example, while working locally on the website, the build configuration is set to Debug. When things look good, I go ahead and upload the latest .dll for the website/webapp. Should I instead at that point switch the build configuration to Release, then compile, and then upload that version of the .dll to the server?

我希望这个问题是'重复。我在这个主题中阅读了一些其他类似的话题，但没有发现与我的问题有直接关系的东西。

I hoping this question isn't a duplicate. I read a number of other questions with similar words in the subject, but didn't find something directly related to my question.

谢谢，

Adam

推荐答案

使用调试程序集运行对性能有点重要，因为它们占用更多记忆，但通常不是极端的。只有当它真的是一个发行版时，才应该部署一个版本。如果您仍然预期在野外的某些级别的意外行为，我会考虑使用调试程序集，因此您将从未处理的异常获取更多有用的信息。真正的性能gotcha在您的web.config中具有 debug =true。

Running with debug assemblies is a little heavier on performance, as they take up more memory, but usually not extremely so. You should only deploy a release build when it's really a "release". If you still anticipate some level of unexpected behavior in the wild, I'd consider using debug assemblies, so you will get more useful information from unhandled exceptions. The real performance "gotcha" is having debug="true" in your web.config.

这篇关于ASP.NET网站DLL：Debug vs. Release version的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！