作为MS Visual C ++ 2005 ATL合并模块的替代品，我需要分发哪些文件? [英] What files do I need to distribute as an alternative to MS Visual C++ 2005 ATL merge modules?

问题描述

当前，我正在分发包含三个合并模块的软件产品:

Currently I'm distributing a software product that includes three merge modules:

Microsoft_VC80_CRT_x86.msm
ATL.msm
policy_8_0_Microsoft_VC80_ATL_x86.msm

某些客户使用了不喜欢这些MSM文件的打包技术(我认为是因为他们在写入WinSxS时遇到技术问题).我可以直接将dll文件直接分发到应用程序的"Program Files"文件夹中吗，如果需要，则需要哪些dll?只是atl80.dll吗?

Some customers use packaging technology that doesn't like these MSM files (I think because they have technical problems with them writing to WinSxS). Can I just distribute the dll files directly into my application's Program Files folder, and if so which dlls do I need? Is it just atl80.dll?

推荐答案

您的替代方法是为该版本的Visual Studio运行VC_redist.exe，并使用您使用的任何设置工具从引导程序中运行它.

Your alternative is to run the VC_redist.exe for that version of Visual Studio, run it from the bootstrapper with whatever setup tool you're using.

我不知道您对包装技术的含义.可以安装合并模块(msm文件)的唯一方法是在构建时将它们添加到MSI文件构建中.换句话说，唯一相关的打包技术是Windows Installer和MSI文件.因此，您需要确切地找出此问题是什么.每个人都使用合并模块或VC_redist.exe，因为这是唯一可靠的操作.

I don't know what you mean about packaging technology. The only way merge modules (msm files) can be installed is to add them at build time to an MSI file build. In other words, the only packaging technology that's relevant is Windows Installer and MSI files. So you need to find out exactly what this issue is. Everyone uses the merge modules or the VC_redist.exe because it's the only reliable thing to do.

以非官方方式自行执行操作的一个问题是Windows Update无法找到它们(这适用于静态链接).因此，当Microsoft将安全修复程序应用于这些Dll时，您将使客户容易受到攻击.

One issue with doing it yourself in an unofficial way is that Windows Update can't find them (and that applies to static linking to). So when Microsoft applies a security fix to those Dlls then you are leaving your customers vulnerable.

这篇关于作为MS Visual C ++ 2005 ATL合并模块的替代品，我需要分发哪些文件?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！