MSDeploy是否“友好"?足够,或者可以将其包装在MSI文件中 [英] Is MSDeploy "friendly" enough, or can it be wrapped up in an MSI file

查看:90
本文介绍了MSDeploy是否“友好"?足够,或者可以将其包装在MSI文件中的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您认为MSDeploy软件包是向最终用户提供在其系统上安装Web应用程序的好选择.例如,与使用MSI文件安装Web应用程序的体验相比,该体验如何?

In your opinion, are MSDeploy packages a good option for giving to an end user to install a webapplication on their system. How does it compare with, say, the experience of using an MSI file to install a web app?

是否有人尝试将MSDeploy程序包包装在MSI程序包中?会行吗?

Has anybody tried wrapping up an MSDeploy package inside an MSI package? Would it work?

推荐答案

在我看来,MSDeploy是一种工具,可以帮助在计算机之间同步网站,就像AppCenter用来将配置良好的主服务器复制到许多计算机上一样. Windows Installer(用于IIS和SQL配置的MSI + WiX CustomActions)是关于将软件包应用到修改事务状态的计算机上的.它遵循更传统的打包软件模型.

MSDeploy was described to me as a tool that helps synchronize web sites between machines, much in the way that AppCenter used to replicate a well configured master to many machines. The Windows Installer (MSI + WiX CustomActions for IIS and SQL config) is about applying packages to a machine that modify state in a transaction. It follows the more traditional packaged software model.

这是解决机器配置问题的两种不同方法.每个都针对一组不同的要求进行了优化. MSDeploy =正在复制计算机状态. MSI =应用交易中的更改.

Those are two different approaches to the problem of configuring machines. Each is optimized around a different set of requirements. MSDeploy = replicating machine state. MSI = apply changes in transaction.

您可以将MSDeploy放入MSI吗?大概.会运作良好吗?也许,如果您忽略有关交易的部分.我认为这是关键的区别.在要声明要分发的配置并使其完全应用或根本不应用(即不以中间/无效状态结束)的环境中,基于软件包的安装似乎是合适的.

Could you throw MSDeploy into an MSI? Probably. Would it work well? Maybe, if you ignore the part about transaction. That in my mind is the key difference. In environments where you want to declare the configuration you want distributed and have it either apply fully or not apply at all (i.e. don't end up in an intermediate/busted state) then package based installation seems appropriate.

如果您有一台配置正确的机器,并且想要使一堆机器看起来像它(并且愿意使发生故障的机器停止旋转,并重复该过程直到被提交之前),那么MSDeploy似乎合适的.

If you have a machine that you configured just right and want to make a bunch of machines look like it (and are willing to take a failed machine out of rotation and repeat the process until it is beaten into submission) then MSDeploy seems appropriate.

您的问题中没有足够的信息来建议哪种方法更好...但是我认为它们并没有在一起. < smile/>

There isn't enough information in your question to suggest which works better... but I don't think they go together. <smile/>

这篇关于MSDeploy是否“友好"?足够,或者可以将其包装在MSI文件中的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆