在package.manifest中向VCLibs.110添加依赖项后无法部署 [英] Cannot deploy after adding dependency to VCLibs.110 in package.manifest

问题描述

首先我得到了app认证工具包测试错误。在package.manifest中向VCLibs.110添加依赖项后，这些错误消失了。但我部署应用程序时遇到问题。

以下是新错误：

错误  2  Windows无法安装包********** ********因为这个包依赖于另一个无法找到的包。此程序包要求任何发布者发布的最低版本11.0.0.0的框架Microsoft.VCLibs.110;
在64位计算机上，必须安装每个框架的32位和64位版本才能安装该程序包。提供框架以及此包。 

解决方案

您永远不必明确添加对VCLib的引用。 如果您正在制作C ++应用程序，则只需在部署文件夹下创建一个子目录，如：YourApp_X.0.0.0_Win32_Debug_Test \ Dependencies \ X86和X64。 

我认为您应该恢复到应用认证套件测试错误。 你能粘贴你得到的错误，以及你正在使用什么类型的应用程序吗？

谢谢，

马特

First I got app certification kit test errors. After adding dependency to VCLibs.110 in package.manifest, these errors are gone. But I have problem to deploy the app.

Here is the new error:

Error 2 Windows cannot install package ****************** because this package depends on another package which could not be found. This package requires minimum version 11.0.0.0 of framework Microsoft.VCLibs.110 published by any publisher to install; On 64-bit machines, both 32-bit and 64-bit versions of each framework must be installed to install the package. Provide the framework along with this package. 

解决方案

You should never have to explicitly add references to the VCLibs.  If you are making a C++ app, you will simply get a subdirectory created under your deployment folder like : YourApp_X.0.0.0_Win32_Debug_Test\Dependencies\X86 and X64. 

I think you should revert back to the app certification kit test errors.  Can you paste the error(s) you were getting, and what kind of app you are working on?

Thanks,
Matt

这篇关于在package.manifest中向VCLibs.110添加依赖项后无法部署的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！