管理所有新应用？ [英] Managed for all New Apps?

问题描述

对于所有新的桌面应用程序，是否推荐了托管/ CLR？即对于新的桌面应用程序，一般不建议使用原生MFC / Win32

？一般来说，不是

指的是异常（例如司机）

-

Greg McPherran
www.McPherran.com

解决方案

"格雷格" < [e-mail]>在留言中写道

新闻：BC ********************************** @ microsof t.com ...

对于所有新的桌面应用程序是管理/ CLR推荐的吗？


推荐给谁？在什么平台上？使用什么样的假设。


如果.Net平台提供了所需的一切，那么负责开发新应用程序的那些技能是否符合什么？是必需的，

如果所有目标机器都安装了平台，如果它提供了所有必要的性能，那么使用它似乎是有意义的。 br />
即原生MFC / Win32一般不推荐用于新的桌面应用程序吗？一般来说，不是说引用例外（例如司机）

我认为这个世界太复杂了，不能成为一个二元的

命题 - 驱动程序C，应用程序C ++ / CLI。


问候，

将

>如果.Net平台提供了所需的一切

即使它没有。使用C ++，你也可以根据需要使用原生库。

这对决定几乎没有影响。

如果那些负责开发的人的技能新的应用程序与所需的内容一致
如果.NET被认为是新的推荐（这是我最初要求的b
），那么公司将使用过时的旧技术只是因为

人们可能需要加快速度吗？同样，这几乎没有影响。

如果它提供了所有必要的性能
再次使用C ++可以根据需要使用原生，所以这又是一个NOP。

如果所有目标机器都安装了平台
再次，所以一家公司将开发一个基于过时的
技术的应用程序，而不是安装免费的Framework！

框架甚至可以通过安装和自动检测安装。

再次NOP。


所以，我会重复我原来的问题。 .NET推荐使用新的

桌面应用程序而不是MFC等吗？

-

Greg McPherran
www.McPherran.com

" William DePalo [MVP VC ++]" ;写道：

" Greg" < [e-mail]>在消息中写道
新闻：BC ********************************** @ microsof t.com。 ..

对于所有新的桌面应用程序是管理/ CLR推荐？

推荐给谁？在什么平台上？使用什么样的假设。

如果.Net平台提供了所需的一切，如果负责开发新应用程序的技能与所需的技能一致，
如果所有目标机器都安装了平台，如果它提供了所有必要的性能，那么使用它似乎是有意义的。

即原生MFC / Win32一般不推荐用于新的桌面应用程序吗？一般来说，不是指引例外（例如司机）

我认为这个世界太复杂了，不能成为一个二元的命题 - 司机C，应用程序C ++ / CLI。

问候，

Greg写道：

所以，我会重复我原来的问题。 .NET推荐用于新的桌面应用程序而不是MFC等吗？

由谁推荐？我确定C＃团队会推荐这个。我不是这样对于C ++团队确实如此。


严重的是，WinForms 2.0缓解了1.x的许多缺点。

我们正在使用Winforms开发最终用户GUI应用程序，并且没有可以追溯到CLR的重要性能问题。对于许多

应用程序来说，这已经足够了。 MFC在你最终会做什么以及你将获得的性能方面仍然更好，但大多数应用都不需要以最快的速度获得
或者逐像素控制他们的GUI外观。


对于某些桌面应用程序，我会去.NET，对于其他人，我还是会去MFC（或WTL） ）。


-cd

For all new desktop apps is managed/CLR recommended? I.e. Native MFC/Win32
not recommended in general for new desktop apps? Speaking in general, not
referring to exceptions (e.g. drivers)
--
Greg McPherran
www.McPherran.com

解决方案

"Greg" <[e-mail]> wrote in message
news:BC**********************************@microsof t.com...

For all new desktop apps is managed/CLR recommended?
Recommended for whom? On what platforms? Using what set of assumptions.

If the .Net platform provides everything one needs, if the skills of those
tasked with developing the new applications coincide with what is required,
if all of the target machines have the platform installed, if it provides
all of the performance necessary, it seems it would make sense to use it.
I.e. Native MFC/Win32 not recommended in general for
new desktop apps? Speaking in general, not
referring to exceptions (e.g. drivers)

I think that the world is far too complicated for this to be a binary
proposition - drivers C, applications C++/CLI.

Regards,
Will

> If the .Net platform provides everything one needs
Even if it doesn''t. with C++ you can also use native libraries as needed so
this has little/no impact on the decision.

if the skills of those tasked with developing the new applications coincide with what is required If .NET is considered the new recommendation (which is what I am originally
asking), what company is going to use an outdated old technology just because
people may need to come up to speed? Again, this has little/no impact.
if it provides all of the performance necessary Again with C++ can use native as needed so again this is a NOP.
if all of the target machines have the platform installed Again, so a company is going to develop an app based on an outdated
technology instead of installing the freely available Framework!! The
framework can even be deployed with the install and auto-detect on install.
Again a NOP.

So, I''ll repeat my original question. Is .NET recommended in general for new
desktop applications instead of MFC etc.?
--
Greg McPherran
www.McPherran.com
"William DePalo [MVP VC++]" wrote:
"Greg" <[e-mail]> wrote in message
news:BC**********************************@microsof t.com...

For all new desktop apps is managed/CLR recommended?

Recommended for whom? On what platforms? Using what set of assumptions.

If the .Net platform provides everything one needs, if the skills of those
tasked with developing the new applications coincide with what is required,
if all of the target machines have the platform installed, if it provides
all of the performance necessary, it seems it would make sense to use it.

I.e. Native MFC/Win32 not recommended in general for
new desktop apps? Speaking in general, not
referring to exceptions (e.g. drivers)

I think that the world is far too complicated for this to be a binary
proposition - drivers C, applications C++/CLI.

Regards,
Will

Greg wrote:

So, I''ll repeat my original question. Is .NET recommended in general
for new desktop applications instead of MFC etc.?

Recommended by whom? I''m sure the C# team would recommend that. I''m not so
sure about the C++ team.

Seriously though, WinForms 2.0 alleviates many of the shortcomings of 1.x.
We''re developing an end-user GUI application with Winforms and have no
significant performance issues that can be traced to the CLR. For many
apps, it''s good enough. MFC is still better in terms of what you can
ultimately do and the performance you''ll get, but most apps don''t need to be
the very fastest or to have pixel by pixel control of their GUI appearance.

For some desktop apps, I''d go .NET, for others, I''d still go MFC (or WTL).

-cd

这篇关于管理所有新应用？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！