当前位置：文江博客话题详情

C# 缺少 MSVCR100.dll

发布于 2024-11-28 05:54:51 字数 192 浏览 3 评论 0原文

我正在开发一个执行另一个应用程序的应用程序，但收到此错误：

程序无法启动，因为您的 MSVCR100.dll 丢失计算机

上装有我的 C# 应用程序，我可以通过将此 .dll 复制到 windows/system32 文件夹来解决此问题吗？或者存在另一种方法来做到这一点？

原文

分享到QQ

分享到微博

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

发布评论

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

蓦然回首 2024-12-05 05:54:51

下面的链接指向 MSVCRT100 安装程序的正确下载。这可能是您希望客户在安装应用程序之前运行的内容。这会将 MSVCRT DLL 正确安装在正确的目录中，以便所有应用程序都可以使用它。

Microsoft Visual C++ 2010 Redistributable Package (x86)（可能是 32 位所需的和 64 位操作系统）

Microsoft Visual C++ 2010 Redistributable软件包 (x64)（仅当您的应用程序本身是 64 位时）

如果您确实想通过自己的 MSI 中的合并模块安装 MSVCRT100 DLL - 您可以将您的 MSI 链接到位于x86 版本的“c:\program files\common files\merge module”目录”（假设您安装了 Visual Studio 2010）。

C:\Program Files (x86)\Common Files\Merge Modules>dir *CRT*.msm
 Volume in drive C has no label.
 Volume Serial Number is 60A4-1718

 Directory of C:\Program Files (x86)\Common Files\Merge Modules

04/22/2011  01:18 PM           584,192 Microsoft_VC100_CRT_x64.msm
04/22/2011  01:41 PM           571,904 Microsoft_VC100_CRT_x86.msm  <-- This is likely the MSM you want if your app is 32-bit.
04/22/2011  01:14 PM           847,360 Microsoft_VC100_DebugCRT_x64.msm
04/22/2011  01:39 PM           801,792 Microsoft_VC100_DebugCRT_x86.msm

另外两个替代方案：
不要将 MSVCRT100.dll 复制到系统目录中，而是将其复制到您尝试启动的依赖于此 DLL 的 EXE 应用程序的目录中。不建议这样做，但不会冒破坏其他应用程序的风险。

另一种选择。如果您实际上拥有尝试启动的 EXE 的源代码，则只需静态链接到它就可以完全绕过所有这些“安装 msvcrt100.dll”噪音。在 Visual Studio 中，它是 C/C++ 下项目属性对话框中的选项（在“代码生成”选项卡下）。将“运行时库”从“多线程 Dll”更改为“多线程”。这会添加 /MT 编译器开关。

This links below point to the proper downloads for the MSVCRT100 installer. This is likely what you want your customers to run before installing your app. This will properly install the MSVCRT DLLs in the proper directory such that all applications can use it.

Microsoft Visual C++ 2010 Redistributable Package (x86) (probably what you need for 32-bit and 64-bit os)

Microsoft Visual C++ 2010 Redistributable Package (x64) (Only if your app itself is 64-bit)

If you actually want to install the MSVCRT100 DLLs through a merge module within your own MSI - you can link your MSI to the MSMs that are located in the x86 version your "c:\program files\common files\merge modules" directory" (Assuming you have Visual Studio 2010 installed).

C:\Program Files (x86)\Common Files\Merge Modules>dir *CRT*.msm
 Volume in drive C has no label.
 Volume Serial Number is 60A4-1718

 Directory of C:\Program Files (x86)\Common Files\Merge Modules

04/22/2011  01:18 PM           584,192 Microsoft_VC100_CRT_x64.msm
04/22/2011  01:41 PM           571,904 Microsoft_VC100_CRT_x86.msm  <-- This is likely the MSM you want if your app is 32-bit.
04/22/2011  01:14 PM           847,360 Microsoft_VC100_DebugCRT_x64.msm
04/22/2011  01:39 PM           801,792 Microsoft_VC100_DebugCRT_x86.msm

Two other alternatives:
Instead of copying MSVCRT100.dll into a system directory, copy it into the directory of the EXE app you are trying to launch that depends on this DLL. This isn't recommended, but won't run the risk of breaking other apps.

Another alternative. If you actually have the source code to the EXE that you are trying to launch, you can completely bypass all of this "install msvcrt100.dll" noise by just statically linking to it. In visual studio, it's the option in the project's propery dialog under C/C++ (under the Code Generation tab). Change "runtime library" from "Multi-threaded Dll" to just "Multi-threaded". This adds the /MT compiler switch.

回复收藏 0 原文