部署商业桌面 .NET 应用程序有哪些选项?

发布于 2024-09-30 18:29:49 字数 646 浏览 3 评论 0原文

肯定还有许多其他开发人员正在寻找部署 .NET 桌面应用程序的“好”方法,其中“好”的意思是:

  • 试用用户易于安装
  • 下载大小合理(不是 350 MB 的怪物)
  • 任何购买工具的成本低廉
  • 针对 Windows XP SP3、Windows Vista、Windows 7 等。

如果用户必须如果跳过太多的环节,或者下载时间太长,用户就不会尝试该软件,也永远不会发现它有多棒/有用。所以这是主要的考虑因素。

其他相关因素:

  • 开发环境:Visual Studio 2010 或 2008(可以切换)
  • 安装要求很简单:没有 Visual Studio Installer 无法处理的。
  • 学习曲线:非常需要演练类似的 .NET 部署。
  • 尽管当前针对的是 .NET 2.0,但无需重新启动(安装 Windows Installer 3.1!)即可针对更高版本的 .NET(4.0 客户端配置文件?)可能有用/可取。

据我所知,所有纯微软方法都涉及多个文件来制作复杂的安装说明(下载 X、Y、运行 X、整理)。

There must be many other developers looking for a "good" method of deploying a .NET desktop application, where "good" means:

  • Ease of installation for a trial user
  • Reasonable download size (Not a 350 MB monstrosity)
  • Low cost of any purchased tool
  • Targets Windows XP SP3, Windows Vista, Windows 7, etc.

If a user has to jump through too many hoops, or the download takes too long, the user won't try the software and will never find out how great/useful it is. So this is the major consideration.

Other relevant factors:

  • Development environment: Visual Studio 2010 or 2008 (can switch)
  • Installation requirements are simple: nothing Visual Studio Installer can't handle.
  • Learning curve: a walk-through of a similar .NET deployment is highly desirable.
  • Although currently targeting .NET 2.0, targeting a later version of .NET (4.0 client profile?) without reboots (Windows Installer 3.1 install!) might be useful/desirable.

As far as I can tell, all pure Microsoft approaches involve multiple files making for complex installation instructions (download X, Y, run X, tidy up).

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

楠木可依 2024-10-07 18:29:49

我不记得确切的机制,但您可以将安装程序设置为直接从 Microsoft 下载 .NET 框架,而不是从您自己的站点下载,并且前提是尚未安装该框架。

此外,请考虑以客户端配置文件为目标,该配置文件“仅”50 MB(仍然很大,但优于 350 MB)。最后,Windows Vista 和 Windows 7 预装了 .NET,微软也在自己的一些软件中使用它,因此该框架的渗透率实际上相当高。如今,用户需要将框架与应用程序一起安装的情况要少得多,至少只要您坚持使用 2.0 或 3.5。

I don't remember the exact mechanics, but you can set your installer to download the .NET framework directly from Microsoft, rather than your own site, and only if it's not already installed.

Additionally, look into targeting the Client Profile, which is "only" 50 MB (still large, but better than 350 MB). Finally, Windows Vista and Windows 7 ship with .NET pre-installed, and Microsoft is using it in some of their own software, so penetration of the framework is actually pretty high. It's much rarer these days for a user to need to install the framework along with your application, at least as long as you stick with 2.0 or 3.5.

薯片软お妹 2024-10-07 18:29:49

如果目标计算机中存在 Windows Installer 3.1 或更高版本并且 .NET Framework,则使用安装项目创建安装程序对我来说是非常简单的体验。

结果是一个可供下载和运行的 MSI 文件。您只需将项目输出添加到设置项目中就可以了。

如果您坚持使用 .NET 2.0,我相信它比 .NET 3.5 SP1 小。

另一种选择是XCOPY。您压缩应用程序的 bin 文件夹并要求用户解压缩并运行该应用程序。

If Windows Installer 3.1 or later and .NET framework is present in the target machine, creating an installer using Setup projects was a pretty straightforward experience for me.

The result is a single MSI file to download and run. You just add the project output to the setup project and you are good to go.

If you stick to .NET 2.0, I believe it was smaller than .NET 3.5 SP1.

Another alternative is XCOPY. You compress the bin folder of the application and ask the user uncompress and run the application.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文