使用MSP补丁添加丢失的文件 [英] Add missing file with msp patch

问题描述

我创建了一个安装程序，并部署到我们的测试环境中，由于缺少dll(在wsx文件中未包含该文件)而出现错误.是否可以创建一个MSP补丁来运送丢失的dll，还是只创建一个全新的安装程序会更好呢?

I created an installer, deployed to our test environment and got an error due to a missing dll (it was not included in the wsx file). Is it possible to create a MSP patch to ship the missing dll or is it better to simply create a whole new installer?

我尝试了以下各种示例，但始终出现此错误:

I tried following various examples but I keep getting this error:

调试:错误2356 :无法在流媒体:media1.cab中找到机柜.

DEBUG: Error 2356: Couldn't locate cabinet in stream: media1.cab.

推荐答案

补丁程序可以执行更新的MSI可以执行的任何操作，但这只是一种打包和交付机制，可以以更紧凑的方式交付更新.因此，您实际上必须创建安装程序的完整版本，然后才能将此新更新打包为补丁程序.

A patch can do anything an updated MSI can do, but it is merely a packaging and delivery mechanism that delivers an update in a more compact way. Hence you must actually create a full new version of your setup to be able to then package this new update as a patch.

重要提示:在完全升级正常工作之前，不要花时间测试所有修补程序.这完全是浪费时间.它只会产生神秘的错误，是现实世界中非常普遍的时间消耗.

除非您以前的安装已经投入生产，因此无用"，否则我不会在补丁上浪费时间.修补程序需要大量的时间来创建，并且需要更多的时间进行测试-大量的风险和复杂性，并且它仅是一种便捷的方式，可以发布小的更新(例如您描述的内容)，而不必分发可能巨大的新MSI文件.除非您的产品非常庞大且需要花很长时间才能安装，否则通常不使用补丁来进行UAT或QA测试.

Unless your previous setup has gone to production and hence is "out in the wild", I wouldn't waste my time with a patch. Patches require a lot of time to create and even more time to test - there is a lot of added risk and complexity, and it is only intended to be a convenient way to deliver small updates such as what you describe without having to distribute a potentially huge, new MSI file. It is not common to use patches for UAT or QA testing unless your product is really huge and takes ages to install.

我个人认为，MSI在修补方面完全失败了.它应该是一个易于使用的增值功能，但它本身已成为一个非常复杂，有问题的问题.

Personally I feel that MSI has failed entirely when it comes to patching. It should be an easy to use, value added feature, but it has become a hugely complicated, problematic issue in its own right.

这篇关于使用MSP补丁添加丢失的文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！