如何使用.net安装程序创建wpf安装程序 [英] how can i create the wpf setup with .net installer

问题描述

大家好，

我开发了wpf应用程序.

如何使用以下选项创建设置

Project =>属性=>发布=>前提条件=> .Net Framework 3.5 SP1和Windows Installer 3.1 with
从与我的应用程序相同的位置下载必备软件

让我知道细节


在此先感谢..........

hi all,

i am developed the wpf application.

how to create setup with below option

Project=>Properties=>Publish=>Prerequisites=>.Net Framework 3.5 SP1 & Windows Installer 3.1 with
Download prerequisites from the same location as my application

Let me know the details


Thanks in advance..........

推荐答案

WPF是.NET的一部分.因此，您的问题毫无道理.如果未安装.NET，则无法使您的应用正常运行，您需要安装它.除了.NET之外，没有WPF设置.

WPF is part of .NET. Therefore your question makes no sense. There is no way to make your app work without .NET installed, you need to install it. There is no WPF setup apart from .NET.

您需要安装.NET Framework 3.0或更高版本，建议安装4.0.根据Microsoft文档，即使.NET Framework Client Profile应该包含WPF，我也将安装该框架的完整版本:
http://msdn.microsoft.com/en-us/library/cc656912.aspx [ ^ ].

对我来说，该文档没有提供令人信服的事实来证明.NET Framework Client Profile.我认为针对客户端应用程序进行了优化"，更快的部署"和较小的安装包"(受什么因素影响)的说法并没有事实依据，对我而言并不重要. 不知道这些因素引起问题的情况.子集是一个子集，语句它为最提供功能[阅读:不是全部"-SA]客户端应用程序看起来比所有其他有前途的声明更令人恐惧.

微软过去有很多死胡同的产品和技术.时间证明，它们证明是无用的，只不过是用遗留的遗产污染了系统.一些技术是由另一家公司引入的，并由Microsoft和其他公司使用，并且几乎被放弃了.我碰巧避免使用其中许多.例子? DDE，NetDDE，NetBIOS，IPX/SPX，NetBEUI，OLE…也许我遗漏了一些东西，但是此刻我的直觉告诉我.NET Framework客户端配置文件不会持续很长时间.当然，我可能会误会.过一会儿检查会很有趣... :-)



我真的不明白没有.NET Framework(客户端配置文件)时如何在客户端系统中安装安装程序"的问题.我是否应该理解它，以便您希望完全不安装框架就运行您的应用程序?如果是这样，那就算了.您需要将客户端安装.NET作为先决条件.或者，您可以随应用程序一起分发框架.

请参阅:
http://msdn.microsoft.com/en-us/library/6hbb4k3e.aspx [ ^ ].

—SA

You need to install .NET framework 3.0 or later, 4.0 recommended. I would install full version of the framework, even though .NET Framework Client Profile is supposed to include WPF, according to Microsoft documentation:
http://msdn.microsoft.com/en-us/library/cc656912.aspx[^].

To me, this documentation does not provide convincing facts justifying .NET Framework Client Profile. I don''t see factual support of the claim that it is "optimized for client applications", and "faster deployment" and "smaller install package" (by what factor?) don''t look critically important to me — I don''t know the case where those factors caused a problem. Subset is a subset, and the statement "It provides functionality for most [read: "not all" — SA] client applications" looks much more scary than all other claims promising.

Microsoft had a lot of dead end products and technologies in the past; and the time proved they turn out to be useless, only contaminating the systems with dead legacy. Some technologies were introduced by other company, used by Microsoft and others and were pretty much abandoned. I happen to avoid using many of them. Examples? DDE, NetDDE, NetBIOS, IPX/SPX, NetBEUI, OLE… Maybe I''m missing something, but at this moment my intuition tells me that .NET Framework Client Profile won''t last for long. I may be mistaken, of course. Would be interesting to check it up after a while… :-)



I don''t really understand the question "without .NET Framework (client profile) how can I install the setup in client system?". Should I understand it so that you hope to run your application without installing the framework at all? If so, just forget it. You need to required the client for the .NET installation as a prerequisite. Alternatively, you can distribute the framework with your application.

Please see:
http://msdn.microsoft.com/en-us/library/6hbb4k3e.aspx[^].

—SA

这篇关于如何使用.net安装程序创建wpf安装程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！