MSIX软件包可以使用外部文件进行用户设置吗？ [英] Can a MSIX package use an external file for user settings?

问题描述

我们正在评估从当前客户端/服务器应用程序到.NET Core的迁移。 3.0版本增加了对客户端所需的WinForms的支持，但不支持ClickOnce。
我们的解决方案是在本地安装的，我们需要包括其他设置，例如应用程序服务器的地址。我们动态创建ClickOnce程序包，可用于安装和更新客户端并包括设置。今天，这就像一种魅力。用户使用ClickOnce软件包安装客户端，并且每次我们更新软件时，都会在客户的站点上重新生成这些软件包，并且他们会使用正确的设置自动获得新版本。

We are evaluating the migration from our current client/server application to .NET Core. The 3.0 release added the support for WinForms we need for our client, but ClickOnce will not be supported. Our solution is installed on-premise and we need to include settings (among others) like the address to the application server. We create dynamically ClickOnce packages that can be used to install and update the clients and include the settings. This is working like a charm today. The users install the client using the ClickOnce package and every time we update the software we regenerate these packages at the customer's site and they get automatically the new version with the right settings.

我们正在考虑使用MSIX作为替代方案，但是我们有一个问题：
-是否可以向安装时将使用（部署）的MSIX软件包中添加一些外部设置文件？

We are looking at MSIX as an alternative, but we have got a question: - Is it possible to add some external settings files to the MSIX package that will be used (deployed) when installing?

该软件本身的软件包可以静态生成，但是在第一次安装/更新时如何将设置分发给客户端？

The package for the software itself could be statically generated, but how could we distribute the settings to the clients on first install / update?

推荐答案

MSIX支持修改程序包。这很接近您想要的，在安装您的应用程序的主要MSIX软件包后 安装一个单独的软件包即可完成自定义。

MSIX has support for modification packages. This is close to what you want, the customization is done with a separate package installed after you install the main MSIX package of your app.

它不能与主应用程序同时安装。尝试安装修改包时，操作系统会检查是否已安装主应用程序，如果在计算机上找不到主应用程序，它将拒绝安装。

It cannot be installed at the same time as your main app. The OS checks if the main app is installed when you try to install the modification package and it will reject its installation if the main is not found on the machine.

修改软件包是一个独立的软件包，安装在单独的位置。检查我包含的链接，有一个PS窗口的屏幕快照，您可以在其中看到主软件包的安装路径，并且修改后的路径也不同。

The modification package is a standalone package, installed in a separate location. Check the link I included, there is a screenshot of a PS window where you can see the install path for the main package and the modification are different.

在运行时（当用户启动应用程序），操作系统知道这两个软件包已连接并合并了它们的虚拟文件和注册表系统，因此应用程序认为所有资源都在一个软件包中。

At runtime (when the user launches the app) the OS knows these two packages are connected and merges their virtual files and registry system, so the app "believes" all the resources are in one package.

这意味着您可以分别更新主应用程序和修改包，并根据需要部署它们。

This means you can update the main app and the modification package separately, and deploy them as you wish.

如果我们更新了修改包本身（无需接触主包），是否会重新安装到使用它的所有客户端？

And if we update the modification package itself (without touching the main), will it be re-installed to all the clients that used it?

部署更新？您想通过互联网使用自动更新工具吗？还是这些用户在公司内部网络内部进行管理，并从诸如SCCM之类的工具中获取所有应用程序更新？

How do you deploy the updates? Do you want to use an auto-updater tool over the internet? Or ar these users managed inside an internal company network and get all the app updates from tools like SCCM?

修改包主要是供IT部门使用的，

The modification packages were designed mostly for IT departments to use them, and this is what I understood you would need too.

修改包是通过SCCM或其他工具部署的，就像主包一样，没有区别。

A modification package is deployed via SCCM or other tools just like the main package, there are no differences.

对于ISV，我相信可选软件包是更好的解决方案。

For ISVs I believe optional packages are a better solution.

这篇关于MSIX软件包可以使用外部文件进行用户设置吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！