什么是新客户端应用程序的最佳选择？ [英] What would be the best choice for new client-side apps?

问题描述

您好，


我一直在阅读MSDN以找出上述问题的答案，

但我想我应该问这个新闻组（因为几乎所有我在MSDN中读取的
似乎都建议我转移到.NET）。


这是'场景：


我们正在创建一个桌面应用程序（也就是说，没有客户端服务器，没有

三层，没有什么，只是一个简单的普通旧桌面应用程序） 。

而不是收缩包装它将在网上发布。因此，

大小的分发很重要，如果可能的话，我们不想用.NET运行时的应用程序添加另外20MB的下载量。


前进的最佳方式是什么？我们应该咬一口

并使用C ++ / CLI吗？或MFC是要走的路？


谢谢，

Ray

解决方案

< blockquote> Ray写道：

您好，


我一直在阅读MSDN以找出问题的答案以上，

但我想我应该在这个新闻组中询问（因为几乎所有我在MSDN中读取的
似乎都建议我转移到.NET）。


这是'场景：


我们正在创建一个桌面应用程序（即没有客户端服务器，没有

三层，没有什么，只是一个简单的普通旧桌面应用程序。）

而不是收缩包装它将在线分发。因此，

大小的分发很重要，如果可能的话，我们不想用.NET运行时的应用程序添加另外20MB的下载量。


前进的最佳方式是什么？我们应该咬一口

并使用C ++ / CLI吗？或MFC是要走的路？


谢谢，

雷

雷：


如果您担心部署规模


MFC

静态链接

InnoSetup


就可以了。我不断增长的应用程序，包括.chm帮助

文件和一堆示例文档文件，重约700 KB。


David Wilkinson

David Wilkinson写道：

< snip>

Ray：


如果您担心部署规模


MFC

静态链接

InnoSetup


就可以了。我不断增长的应用程序，包括.chm帮助

文件和一堆示例文档文件，重约700 KB。


David Wilkinson

谢谢David！


干杯

Ray

>前进的最佳方式是什么？我们应该咬一口

>并使用C ++ / CLI？或MFC是要走的路？

如果你担心部署规模


MFC

静态链接

InnoSetup


就可以了。我不断增长的应用程序，包括.chm帮助

文件和一堆示例文档文件，重约700 KB。

< to David>

不使用其中一种部署类型的原因是什么？
可以使用Visual Studio吗？

我从未遇到过问题。 （仅在VS2003之后才使用它们。）


<到Ray>

至于选择MFC，这一切都取决于你是否假设你的客户

在他们的系统上是否有.NET运行时，他们是否有
宽带。

你已经假设他们有互联网，因为你提供你的应用程序

下载。

这些天不是大多数人都有宽带？如果您的客户是公司

和高级用户，那么可以肯定地说大多数人都有宽带的b $ b bb，因此如果他们下载.NET运行时没什么大不了的不要
已经拥有它。


如果您选择.NET，您必须判断是否需要大量的互操作
是否包含本机代码。

如果你不是，那么我个人会选择C＃。它更容易学习，

和更友好的用户。


-


亲切的问候，

Bruno van Dooren
br **********************@hotmail.com

仅删除_nos_pam

Hello,

I''ve been reading MSDN to find out the answer for the question above,
but I think I should ask in this newsgroup (since nearly everything I
read in MSDN Seems to recommend me to move to .NET).

Here''s the scenario:

We''re creating a desktop application (that is, no client-server, no
three-tier, no nothing, just a simple plain old desktop application).
Instead of being shrink-wrapped it''ll be distributed online. As such the
size of distribution is important, if possible we don''t want to add
another 20MB download with the app for .NET runtime.

What would be the best way to go forward? Should we just bite the bullet
and use C++/CLI? Or MFC is the way to go?

Thanks,
Ray

解决方案

Ray wrote:

Hello,

I''ve been reading MSDN to find out the answer for the question above,
but I think I should ask in this newsgroup (since nearly everything I
read in MSDN Seems to recommend me to move to .NET).

Here''s the scenario:

We''re creating a desktop application (that is, no client-server, no
three-tier, no nothing, just a simple plain old desktop application).
Instead of being shrink-wrapped it''ll be distributed online. As such the
size of distribution is important, if possible we don''t want to add
another 20MB download with the app for .NET runtime.

What would be the best way to go forward? Should we just bite the bullet
and use C++/CLI? Or MFC is the way to go?

Thanks,
Ray

Ray:

If you are concerned about deployment size

MFC
Static linking
InnoSetup

will do the trick. My ever-growing application, complete with .chm help
file and a bunch of sample document files, weighs in at about 700 KB.

David Wilkinson

David Wilkinson wrote:
<snip>

Ray:

If you are concerned about deployment size

MFC
Static linking
InnoSetup

will do the trick. My ever-growing application, complete with .chm help
file and a bunch of sample document files, weighs in at about 700 KB.

David Wilkinson

Thanks David!

Cheers
Ray

>What would be the best way to go forward? Should we just bite the bullet

>and use C++/CLI? Or MFC is the way to go?

If you are concerned about deployment size

MFC
Static linking
InnoSetup

will do the trick. My ever-growing application, complete with .chm help
file and a bunch of sample document files, weighs in at about 700 KB.

<to David>
What is the reason for not using one of the deployment types that are
available with Visual Studio?
I have never had a problem with them. (only used them since VS2003 though).

<to Ray>
As for choosing MFC, it all depends on whether you assume your customers
have the .NET runtime on their system or not, and whether they have
broadband or not.
You already assume they have internet, since you offer your app for
download.
Don''t most people have broadband these days? If your customers are companies
and power users, it would be safe to say that the large majority has
broadband, so downloading the .NET runtime is no big deal if they don''t
already have it.

And if you choose for .NET, you have to judge if you need a lot of interop
with native code or not.
If you don''t, then I would personally choose for C#. It is easier to learn,
and more user friendly.

--

Kind regards,
Bruno van Dooren
br**********************@hotmail.com
Remove only "_nos_pam"

这篇关于什么是新客户端应用程序的最佳选择？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！