如何维护“忽略/处理后续异常”开发商之间的断点？ [英] How to maintain "Ignore/handle subsequent exceptions" breakpoints between developers?

问题描述

有时，有些代码会出现异常，您不希望在IDE中停止执行（例如设置连接时的OLE异常）。

Sometimes there are pieces of code where exceptions occur that you don't want to stop execution in the IDE (e.g. OLE exceptions when setting up a connection).

诀窍是围绕这个放置2个断点，第一个设置为忽略后续例外，第二个设置为处理后续例外。

The trick is to place 2 breakpoints around this, with the 1st set to "Ignore subsequent exceptions" and the 2nd to "Handle subsequent exceptions".

当您工作正常时是唯一一个在代码上工作的代码，断点与代码一起移动。

This works fine when you are the only one working on the code, the breakpoint moves with the code.

但是，当几个开发人员更新同一个文件并且从/到版本控制导入/导出（在我的情况下，SVN）断点可能会以错误的方式结束，您必须重置它们。

However, when several developers update the same file and you import/export from/to version control (SVN in my case) the breakpoints can end up on the wrong lines and you have to reset them.

这是因为这些断点设置在IDE配置中本地维护有没有人曾经找到一种在开发人员之间维护这些断点的方法？

This is because these breakpoint settings are maintained locally in the IDE configuration.

如何？

使用Delphi XE2作为W32应用程序。

Using Delphi XE2 for W32 apps.

推荐答案

这些断点存储在DSK文件中 - 项目或项目组的文件，取决于IDE中打开的内容。您可以考虑将这些文件添加到版本控制。但是，这可能还有其他重要的缺点。

These breakpoints are stored in a DSK file - either that of the project or that of the project group, depending on what was open in the IDE. You may consider adding those files to the version control. However, this might have other significant drawbacks.

这篇关于如何维护“忽略/处理后续异常”开发商之间的断点？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！