Micro Focus Visual Cobol 调试构建、pdb 和 idy 文件不匹配
我在使用我们的自动构建服务器编译的可视化 cobol 代码时遇到问题。当我将 VS2010 调试器附加到 cobol 程序时，它会提示输入 .idy 文件，但在我的情况下，该文件附加了一个“。输出的 idy 文件的文件名中没有“，我没有”不知道在构建过程中对 idy 文件的引用在哪里被搞乱了。有人有解决这个问题的经验吗？澄清一下，Visual Studio 2010 正在寻找 *.diy" <- 形式的文件，其中不应包含引号。
I'm having an issue with compiled visual cobol code from our automated build server. When I go to attach the VS2010 debugger to the cobol program, it prompts for a .idy file but in my case the file has a " appended to it. The output idy files don't have a " in the filename and I don't know where in the build process the reference to the idy file is getting messed up. Does anyone have experience with this problem? Just to clarify, Visual Studio 2010 is looking for a file of the form *.diy" <- where the quotes should NOT be there.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果 .idy 文件的路径包含空格，则您可能会看到对话框标题中显示的文件名后面附加了一个引号，但这本身与您遇到的问题没有直接关系。
IDY 文件仅由调试构建配置创建，并输出到与程序集相同的位置。除此之外，.idy 文件包含有关程序中字段的信息，例如，当您想要添加监视项时，调试器会使用该文件。
如果您已构建要发布的项目，我不希望系统提示您查找 .idy 文件，因此我的假设是 .idy 文件丢失或位于与可执行文件不同的位置。
有几个简单的问题要问您：
当您取消“查找 IDY”对话框时，您是否会看到源代码 – 您仍然可以单步执行吗？
与可执行文件位于同一位置是否有 .idy 文件？
如果您在 Reflector 中打开可执行文件并反汇编程序集，您将注意到与该类关联的 DebugIDYFile 自定义属性。 IDY 文件的路径与您尝试调试的可执行文件一致吗？
这是一个 ASP.NET 项目吗？
此致，斯科特·尼尔森
If the path to the .idy file contains a space, then you may see a quote appended to the file name that appears in the dialog title but this in itself is not directly related to the problem you’re encountering.
IDY files are created by the debug build configuration only and are output to the same location as your assembly. Amongst other things, the .idy file contains information about fields within your program and is used by the debugger when you want to add a watch item for example.
I would not expect you to be prompted to locate the .idy file if you had built the project for release, so my assumption is that the .idy file is either missing or in a different location to the executable.
A few quick questions for you:
When you cancel the Find IDY dialog do you see the source code – can you still step through?
Is there an .idy file in the same location as the executable?
If you open the executable in Reflector and disassemble your assembly, you will notice a DebugIDYFile custom attribute associated with the class. Is the path to the IDY file consistent with the executable you’re trying to debug?
Is this an ASP.NET project?
Regards, Scot Nielsen