值得在 ASP.NET 中使用 Debug.Assert 吗？
在 ASP.NET 中设置适当的调试环境似乎是一个相当大的麻烦，我只是想知道使用断言是否是正确的方法。 我读了一些内容，发现您需要修改 web.config 才能正确使用断言。 这通常是最好的方法还是有其他更容易使用的调试方法？
我们不使用单元测试框架，因此这与问题并不真正相关。
您如何知道它们正常工作或根本不工作之间的区别？ 目前，我可以在代码中放入断言，但它绝对不会执行任何操作，因为它们没有在 web.config 中配置。 这对我来说似乎很危险。
It seems like a fairly large hassle to set up a proper debug environment in ASP.NET and I'm just wondering if using Asserts are the way to go or not. I've read a bit and saw that you need to modify your web.config to properly use Asserts. Is this usually the best way to go or are there other methods of debugging that might be easier to use?
We don't use a unit testing framework so that isn't really relevant to the question.
How do you know the difference between them working properly or not working at all? Currently I can put in asserts in my code and it will do absolutely nothing because they are not configured in the web.config. This seems dangerous to me.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我会在这里引导您：我应该何时使用 Debug.Assert()？。 有几个很好的答案可以告诉您何时适合使用它们，并且您可以从中找出在您的应用程序中是否值得使用它们。
I would direct you here: When should I use Debug.Assert()?. There are several good answers that can tell you when it's good to use them, and you can figure out from there if it's worth it in your app.
拥有调试断言将确保您的代码是正确的。 正确组合测试用例肯定会对您有所帮助。
一些单元测试框架附带了可以记录消息并抛出断言异常的处理程序。 选择这些框架之一或编写自己的处理程序是您可能需要考虑的事情。 但是，一旦单元测试代码捕获这些异常，就应该记录它们并将其标记为失败。
Having Debug Asserts will ensure your code is correct. With the right combination of test cases will definitely help you.
Several Unit test frameworks come with handlers that can log messages and throw exceptions on asserts. Choosing one of these framework or writing your own handler is something that you may have to think about. But once the Unit test code catches these exceptions, they should be logged and marked as failed.