如何查找项目中的警告总数?

发布于 2024-11-29 12:28:44 字数 231 浏览 0 评论 0原文

我刚刚将一个项目从 .net 1.1 转换为 3.5,并且在错误列表中收到了大量警告。

该程序编译并运行正常,但我认为我应该尝试至少减少大量警告。

问题是错误列表只告诉我前 102 个警告。即使我修复了其中一个,数量仍保持在 102。所以我完全不知道实际上有多少警告。

如果有150个,我想把它们去掉。但如果有 10,000 个,我就没有时间全部修复。

有没有办法查看实际的警告总数?

I've just converted a project from .net 1.1 to 3.5, and I'm being given loads of warnings in the error list.

The program compiles and runs ok, but I think I should probably try to at least reduce this large number of warnings.

The trouble is that the error list only tells me about the first 102 warnings. Even when I fix one, the number stays at 102. So I have absolutely no idea how many warnings there actually are.

If there are 150, I'd like to get rid of them. But if there are 10,000, I don't have the time to fix them all.

Is there a way to see the actual total number of warnings?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

蓝眼睛不忧郁 2024-12-06 12:28:44

已经在板上回答了:

有没有办法在 Visual Studio 2010 中显示所有编译器警告?

我遇到了同样的问题..我只能建议对大块进行注释并逐步启用它们。这样您就可以快速了解警告的实际数量

Was already answered here on the board:

Is there a way to show ALL the compiler warnings in Visual Studio 2010?

I had the same Problem.. i can only suggest to outcomment large blocks and enable them step by step. So you have a quick overview on the real number of Warnings

最美的太阳 2024-12-06 12:28:44

尽管此信息与错误消息相关,但我认为它也适用于警告。答案似乎是:

2006 对于 VS 2010 来说仍然如此:

提供可配置的最大值VB.Net 编译器的错误消息限制

感谢您对此问题的反馈。我们同意这是我们想要改进的事情,因为我们从正在升级项目或尝试在新机器上配置它们的客户那里得到了很多反馈。我们实际上进行了一些实验,但由于跟踪所有错误的开销,它使 IDE 的性能太慢。我暂时将此问题解决为“无法修复”,但我们可能会在 Visual Studio 的未来版本中重新讨论此问题。

Though this information relates to the error messages, I think it holds true for the warnings also. The answer seems to be: NO.

It was "no" in 2006 and it is still true for VS 2010:

Provide configurable maximum error messages limit for VB.Net compiler

Thanks for the feedback on this issue. We agree that this is something that we would like to improve as we get this feedback a lot from customers who are upgrading their projects or trying to configure them on a new machine. We actually performed some experiments where we did this but it made the performance of the IDE too slow because of the overhead of tracking all of the errors. I'm resolving this issue as "Won't Fix" for now but we will likely revisit this in a future version of Visual Studio.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文