.net core 3 wpf/winforms(非MSIX)的安装程序? [英] Installer for .net core 3 wpf/winforms (non MSIX)?

问题描述

因此，我们完成了一些wpf到.net核心的转换，现在我们需要将其中一个作为安装程序交付给外部客户端.以前，我们使用ClickOnce，但.net核心已弃用该方法，因此不会根据MS进行移植，他们建议使用MSIX.但是，正如我们从文档中了解到的那样，即使我们将侧载WPF应用程序，其仍将在具有虚拟文件系统的沙箱中运行.这对我们来说是行不通的，显然，它的设计考虑了UWP + Marketplace交付.我们需要文件系统上的应用程序具有完全访问文件系统的权限，这是旧方法".

So, we finished a few wpf conversions to .net core, and now we have a need to ship one to an external client as an installer. Previously we used ClickOnce, but that has been deprecated in .net core and will not be ported according to MS, with them recommending MSIX. However, as we understood from docs, even though we'll sideload a WPF application it will still run in a sandbox with a virtualized file system. And that is a no go for us, it has obviously been designed with UWP+Marketplace delivery in mind. We need the application on the file system with full access to file system, the "good old way".

我们可以将它们作为zip文件发送并让客户解压缩，但是管理层认为这不是那么专业，因此我们需要类似于msi/clickonce的交付包.是否有人在MSIX之外的核心上交付了应用程序?

We could just ship them as a zip file and have the client unpack, but management deemed that as not-so-professional, so we need a delivery package similar to what msi/clickonce had. Has anyone delivered apps on core outside MSIX?

推荐答案

好吧，显然，我们再次遇到了MS的我们的路还是高速公路"，因此我们只使用了Inno Setup.直到这样的时间，我们将获得正确的安装过程，或者MSIX允许进行无沙盒安装而无需不必要的文件系统抽象，这是必须要做的.

Well, apparently, we are again faced with "our way or the highway" from MS, so we just used Inno Setup. Until such time we get a proper installation process or MSIX allows unsandboxed setup without unnecessary file system abstraction, this will have to do.

这篇关于.net core 3 wpf/winforms(非MSIX)的安装程序?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！