Silverlight、Wpf Web App (xbap) 还是 Click Once?利弊 [英] Silverlight, Wpf Web App (xbap) or Click Once? Pros and Cons

问题描述

我们正在开始一个新项目，我正在尝试决定我们应该采用哪种 Wpf 式的开发/部署策略.在我们的案例中，我们正在研究一个相当复杂的商业应用程序，它将被 100 多位(而不是 1000 多位)人使用，所以我倾向于点击一次应用程序.我的老板喜欢 Silverlight 应用程序的想法，因为它意味着更容易部署.那么我们应该往哪个方向跳呢?

We are starting a new project and I'm trying to decide which of the Wpf-esque develop/deploy strategies we should go with. In our case we are looking at quite a complex business app that will be used by 100s (not 1000s) of people, So I'm leaning towards a click-once app. My boss likes the idea of a Silverlight app as it means easier deployment. So which way should we jump?

答案当然是视情况而定".那么每种方法的优缺点是什么?

The answer is, of course, "it depends". So what are the pros and cons of each?

我将开始滚动(编辑从阿图尔卡瓦略):

银光

• 优点

跨浏览器
不需要完整的框架.
更好地控制用户.如果您的用户登录，您不必担心激活密钥或类似的东西.
它适用于 Windows 和 Mac.
您可以轻松更新所有用户应用程序.

Cross browser
Doesn't require full framework.
Better control of users. If your users login, you dont have to worry with activation keys or similar stuff.
It works on Windows and Mac.
You can update all your users apps easily.

• 缺点

无法与客户端的文件系统等交互
与完整的 Wpf 相比功能较少(有人获得了记录差异的好资源吗?)
单窗口
单机版

Can't interact with client's file system etc
Has less functionality compared with full Wpf (anyone got a good resource that documents differences?)
Single window
Single version

Wpf 网络应用程序 (xbap)

Wpf Web App (xbap)

• 优点

全Wpf.

• 缺点

单一浏览器
需要完整的框架
无法与客户端的文件系统等交互
单窗口
单机版

Single browser
Requires full framework
Can't interact with client's file system etc
Single window
Single version

Wpf 点击一次

• 优点

全Wpf
可以离线工作
多个窗口
多个版本(骗局?)
更好地访问计算机的低级部分
无需停机维护

Full Wpf
Can work offline
Multiple windows
Multiple versions (con?)
Better access to low level parts of the computer
No downtime for maintenance

• 缺点

单一浏览器
需要完整的框架
稍微(?) 更难安装.

Single browser
Requires full framework
Slightly(?) harder to install.

推荐答案

首先，我会评估 Web 客户端(最好是 MVC+jQuery)是否无法完成这项工作...

First, I would evaluate whether a web client (ideally MVC+jQuery) can't do the job...

假设一个完整的客户端是有保证的:

Assuming a full client is warranted:

如果是需要客户端的商业应用，我会倾向于使用完整的框架和 ClickOnce；这里的主要区别(重新部署)是客户端必须安装框架 - 但除此之外，ClickOnce 部署非常轻松.实际上，构建 ClickOnce 清单比 Silverlight 等容易，因为 IDE 几乎会为您完成所有工作；您只需要将文件托管在某处(可以是网址；也可以是网络 UNC).

If it is a business app that demands a client, I would tend to go with the full framework and ClickOnce; the main difference here (re deployment) is that the client must have the framework installed - but past that, ClickOnce deployment is very pain free. Actually, building a ClickOnce manifest is much easier than Silverlight etc, since the IDE will do almost all of it for you; you just have to host the files somewhere (could be a web URL; could be a network UNC).

这让您在客户端获得更多控制权(和权力)，以及更大范围的现有资源可供使用(例如，如果您需要，您可以使用一些旧的 winformWPF 表面上的代码).需要完整的框架"也是最大的好处之一:拥有完整的框架".

This gives you much more control (and power) at the client, as well as a far greater range of existing resources to use (for example, if you need, you can use some legacy winform code on the WPF surface). The "requires full framework" is also one of the largest benefits: "has full framework".

您或许还应该考虑 3.5客户端配置文件"设置；不确定这在现实中有多广泛……但值得了解.

You should also perhaps consider the 3.5 "client profile" setup; not sure how wide-spread this is in reality... but worth knowing about.

这篇关于Silverlight、Wpf Web App (xbap) 还是 Click Once?利弊的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！