Delphi 2006丢失组件包

发布于 2024-07-27 17:41:54 字数 584 浏览 9 评论 0原文

Delphi 2006,每当重新启动时,都会丢失组件包。 这种情况每天都会发生。 我们有自己编写的包含自定义 VCL 组件的组件包。 启动 Delphi 2006 时,没有任何提示。 但是,一旦我打开包含其中一些组件的表单,我就会收到

bds.exe - 无法找到组件

该应用程序无法启动 因为 DclOpusRep2006.bpl 不是 成立。 重新安装应用程序 可能会解决这个问题。

当我尝试重新安装组件包时,可能会发生两件事:

  1. 我得到一个设计包的空列表,并且必须转到 regedit 删除有问题的包,然后才能重新添加它。
  2. 我得到了设计包的列表,它确实向我显示了有问题的包已加载且可用。

该软件包始终在本地驱动器上可用,但不是 Delphi 所在的驱动器上可用。 故障排除方面有什么想法吗?

只是为了根据第一个答案澄清我的问题:我是这个项目的唯一开发人员。 该库已从它仍然驻留的同一位置安装,并且组件包列表中的路径是正确的。

Delphi 2006, whenever started afresh, loses component package. This happens on a daily bases. We have component packages with custom VCL components that we wrote ourselves. When starting up Delphi 2006, nothing is noted. But as soon as I open a form that has some of these components on it, I receive

bds.exe - Unable To Locate Component

This application has failed to start
because DclOpusRep2006.bpl was not
found. Re-installing the application
may fix this problem.

When I then try to reinstall the component package, two things might happen:

  1. I get an empy list of design packages and have to go to regedit to delete the package in question before being able to add it anew.
  2. I get the list of design packages allright and it does show me the package in question as loaded and available.

The package is alsways available on a local drive, yet not the one Delphi resides on. Any ideas in troubleshooting?

Just to clarify my problem based on first answer: I am the sole developer on this project. The library has been installed from the same location it still resides and the path in the component packages list is correct.

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

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

发布评论

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

评论(2

情话墙 2024-08-03 17:41:54

无法找到 BPL 或其依赖项之一。 由于当时 BDS 进程的当前目录,它们可能在安装包的过程中被发现,但后来因为当前目录不同而找不到。

始终确保您的 BPL 及其所有依赖项(静态链接的 BPL 和 DLL)位于系统路径中包含的目录中。

The BPL or one of its dependencies could not be found. They may have been found during the installation of the package because of the current directory of the BDS process at the time but not found later because the current directory was then different.

Always make sure your BPLs and all their dependencies (statically linked BPLs and DLLs) are in a directory which is included in the system path.

征棹 2024-08-03 17:41:54

我猜测可能发生了以下情况:

  • 组件包已安装
  • 文件已移动(或者可能有 2 个或更多开发人员正在使用使用它的项目,并且文件位于其 PC 上的不同位置)
  • 并非所有路径都已更新以反映新位置。

在这种情况下,我的建议是找到引用此组件库的所有项目文件并更新路径。

如果您在一个团队中,并且您的团队成员已将此文件安装到每台计算机上的不同位置,请在所有 PC 上标准化该位置。

I'm guessing the following may have happened:

  • The component package was installed
  • The file was moved (or perhaps 2 or more developers are using projects that use it, and the files live in different locations on their PC's)
  • Not all the paths were updated to reflect the new location.

My suggestion in this case would be to find all the project files that reference this component library and update the path.

If you are on a team and your team members have this file installed to different locations on each machine, standardise the location across all PC's.

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