VS2008中VC ++ .Net中的失望 [英] Disappointment in VC++ .Net in VS2008

问题描述

为什么要让Stan Lippman和Herb Sutter为.Net开发创建一个C ++ / CLI

语言，而微软和VC ++开发团队的b
bb使用C ++ / CLI限制.Net开发到Visual Studio中.Net开发技术的最小子集
，而所有新技术都被赋予C＃而不是？泡泡

已经与VS 2008一起爆发，我们最后坦率地说，由VC ++团队开发人员领导，VC ++不会是一流的

..Net开发语言。在那种情况下，为什么还要使用C ++ / CLI，因为它对于C ++程序员来说几乎没有用处。这是

阵容：


1）ASP .NET，不适用于C ++

开发在VS 2008中被删除。

3）WPF，不是用于C ++，甚至没有为WPF创建控件。

C ++ / CLI。

4）WCF，不适用于C ++。

5）WWF，不适用于C ++

6） LINQ，不适用于C ++。


最后所有高级Web应用程序开发都是从C ++中删除，并且放弃了ATL服务器。


VS 2008是C ++ .Net开发人员在各方面的堕胎。微软现在已经清楚了解消息

，并且假装最终被删除了如果你想要用C ++进行.Net开发，那么就忘了它并开始

用C＃编程&＃。它应该从一开始就很清楚，奇迹般地出现了加载器锁定错误，但现在是透明的。


而不是VC ++ for VS的重大新闻2008年是MFC所有

技术的Vista更新。哎呀，我很高兴我学会了像.Net这样的RAD技术，所以我可以回去做MFC开发。


C ++ / CLI是这样的良好的语言，有如此多的谨慎和聪明的决定，以便它几乎在所有方面都优于C＃，它终于意识到微软从未有过这样的感觉很难过任何C ++计划开发人员都有效地与.Net世界的C＃开发人员竞争。

这只是一个骗局，因此他们可以吸引C ++开发人员并转向

他们走向C＃。


Stan Lippman，Herb Sutter，Brandon Bray和其他人，你们都应该感到羞耻
VC ++直接用于.Net的
编程的死胡同。

解决方案

" Edward Diener" < ed ******************* @ tropicsoft.com写信息

新闻：OU *********** ** @ TK2MSFTNGP04.phx.gbl ...

C ++ / CLI是如此优秀的语言，非常谨慎和聪明

做出的决定使得它几乎在所有方面都优于C＃，它终于意识到微软从来没有任何C ++计划开始有效地与之竞争.Net世界中的C＃开发人员。它只是一个骗局，因此他们可以吸引C ++开发人员并将它们转换为C＃b
。

你怎么了？如果你只知道一种编程语言，那么你就是恐龙。适当时使用C ++。适当时使用C＃。适当时使用其他

语言。别肛门了。克服它。继续。快乐

假期。

Tom Walker写道：

Edward Diener < ed ******************* @ tropicsoft.com写信息

新闻：OU *********** ** @ TK2MSFTNGP04.phx.gbl ...

> C ++ / CLI是一种非常好的语言，做出了如此谨慎和明智的决定因此它几乎在所有方面都优于C＃，最终意识到微软从来没有计划让C ++开发人员有效地与.Net中的C＃开发人员竞争，这是令人遗憾的。
世界。这只是一个骗局，因此他们可以吸引C ++开发人员并将他们转向C＃。

你怎么了？如果你只知道一种编程语言，那么你就是恐龙。适当时使用C ++。适当时使用C＃。适当时使用其他

语言。别肛门了。克服它。继续。快乐

假期。

我非常了解C＃，Java和Python，谢谢。


因此，C ++ / CLI尽管是为.Net编程专门创建的C ++版本，但你不应该拥有相同的视频，这绝对是正常的。

visual Visual Studio IDE中的编程支持主流.Net

技术，C＃和VB .Net拥有，并且任何使用这些主流技术的人都几乎肯定会使用C＃对它们进行编程并且

VB .Net。


这是我的OP的要点。虽然你有一个很好的观点，一个人应该灵活地学习多种编程语言，但我认为这对于程序员在承诺和失望时感到失望是很正常的。

使用编程语言的大肆宣传被一开始就大肆宣传和承诺的人们淘汰了。 C ++ / CLI是创建的，作为C ++程序员在使用

..Net技术作为C＃和VB .Net程序员时处于平等地位的手段，其他它纯粹是a / $
浪费时间IMO。这是承诺，但显然现实是完全不同的。


现在我们被告知并且最明显地显示在当前的VS 2008版本中

将不会发生，C ++ / CLI将被视为第二类

第一名。


C ++社区已被温和地接受了所有

的宣传和虚假承诺。来自微软，以及先前，Borland的
。如果有人反对这种与C＃或VB .Net或Delphi相关的二等处理，所有的C ++语言，他们都会告诉他们b / b
来克服它继续。


我可以用C＃轻松编写.Net技术。这是一个简单的

语言，对于经验丰富的C ++程序员来说非常容易，比如

我自己使用。毕竟，这就是微软想要在第一个

的地方，将C ++程序员转移到C＃以进行.Net

编程。 C ++ / CLI我现在看到的本质上是一个将C ++扔给骨子的一个策略

随着时间的推移会变得越来越无用，并且所有新的.Net技术尽管已经获得了其他.Net语言的优越性，但仍然可以选择使用C＃（和VB .Net）。

> ; C ++ / CLI是一个非常好的语言，有如此多的谨慎和智能

>做出的决定使得它几乎在所有方面都优于C＃，它
很遗憾终于意识到微软从来没有计划让C ++开发人员有效地与.Net世界的C＃开发者竞争。

我同意，C ++ / CLI是一种比C＃更好的语言 - 我永远无法确认
真正理解为什么微软让自己头疼

支持3种通用语言，当1可以完成所有这些。

恕我直言他们用.Net做了很多糟糕的决定 - 但它全是水 - 不是吗？


至少我们知道他们现在知道人们使用C ++来开发所有

本机代码区域中Windows应用程序的各个方面 - 让我们只是

希望他们不要忘记这一点！


Dave

Why bother having Stan Lippman and Herb Sutter created a C++/CLI
language for .Net development when Microsoft, and the VC++ development
team, are so clearly intent on limiting .Net development with C++/CLI to
the smallest subset of .Net development technologies in Visual Studio,
while all of the new technologies are given to C# instead ? The bubble
has burst with VS 2008 and we are instead finally told quite frankly, by
a lead VC++ team developer, that VC++ is not going to be a first-class
..Net development language. In that case why bother with C++/CLI, since
it serves little to no purpose for C++ programmers anymore. Here is the
lineup:

1) ASP .NET, not for C++
2) Web services in .Net, not for C++ and even web services client
development is removed in VS 2008.
3) WPF, not for C++ and even creating controls for WPF is absent for
C++/CLI.
4) WCF, not for C++.
5) WWF, not for C++
6) LINQ, not for C++.

Finally all advanced web application development is remove from C++ with
the abandonment of the ATL Server.

VS 2008 is an abortion for C++ .Net developers in every way. The message
is now clear from Microsoft and the pretense is finally dropped "If you
want to do .Net development in C++, just forget about it and start
programming in C#". It should have been clear from the beginning, with
the miraculously appearing loader lock bug, but now is transparent.

Instead the big news in VC++ for VS 2008 is Vista updates for MFC of all
technologies. Gee, I am sure glad I learned a RAD technology like .Net
so I could go back to doing MFC development.

C++/CLI is such a good language, with so much careful and intelligent
decisions made so that it is superior to C# in almost every way, that it
is sad to finally realize that Microsoft never had any plans for C++
developers to effectively compete with C# developers in the .Net world.
It was just a sop so that they could attract C++ developers and turn
them toward C#.

Stan Lippman, Herb Sutter, Brandon Bray, and others, you should all be
ashamed of yourselves in leading VC++ straight to a dead end of
programming for .Net.

解决方案

"Edward Diener" <ed*******************@tropicsoft.comwrote in message
news:OU*************@TK2MSFTNGP04.phx.gbl...

C++/CLI is such a good language, with so much careful and intelligent
decisions made so that it is superior to C# in almost every way, that it
is sad to finally realize that Microsoft never had any plans for C++
developers to effectively compete with C# developers in the .Net world. It
was just a sop so that they could attract C++ developers and turn them
toward C#.

What''s wrong with you? If you know only one programming language you are a
dinosaur. Use C++ when appropriate. Use C# when appropriate. Use other
languages when appropriate. Stop being anal. Get over it. Move on. Happy
Holidays.

Tom Walker wrote:

"Edward Diener" <ed*******************@tropicsoft.comwrote in message
news:OU*************@TK2MSFTNGP04.phx.gbl...

>C++/CLI is such a good language, with so much careful and intelligent
decisions made so that it is superior to C# in almost every way, that
it is sad to finally realize that Microsoft never had any plans for
C++ developers to effectively compete with C# developers in the .Net
world. It was just a sop so that they could attract C++ developers and
turn them toward C#.

What''s wrong with you? If you know only one programming language you are
a dinosaur. Use C++ when appropriate. Use C# when appropriate. Use other
languages when appropriate. Stop being anal. Get over it. Move on. Happy
Holidays.

I know C#, Java, and Python very well, thank you.

So it is absolutely normal to you that C++/CLI, despite being a version
of C++ expressly created for .Net programming, should not have the same
visual programming support in the Visual Studio IDE for mainstream .Net
technologies that C# and VB .Net have, and that anyone using those
mainstream technologies will almost certainly program them using C# and
VB .Net.

This was the gist of my OP. While you have a good point that one should
be flexible in learning more than one programming language, I think it
is quite normal for programmers to be disappointed when the promise and
hype of using a programming language soons becomes obsoleted by the very
same people who hyped and promised in the first place. C++/CLI was
created as a means for C++ programmers to be on equal footing when using
..Net technologies as C# and VB .Net programmers, else it is purely a
waste of time IMO. That was the promise but evidently the reality is
completely different.

Now we are told and most obviously shown in the current VS 2008 release
that it will not happen, that C++/CLI will be treated as a second class
..Net language, by the very same people who created and hyped C++/CLI in
the first place.

The C++ community has been tamed into a meek and mild acceptance of all
of the propaganda and false promises which come down from Microsoft and,
previously, Borland. If anyone objects to this second-class treatment in
relation to C# or VB .Net or Delphi, all inferior languages to C++, they
are told to get over it and move on.

I can easily program the .Net technologies in C#. It is a simple
language and supremely easy for an experienced C++ programmer such as
myself to use. After all, that is what Microsoft wanted in the first
place, to move C++ programmers to C# for the purpose of doing .Net
programming. C++/CLI I see now as essentially a ploy to throw C++ a bone
which will become more and more worthless to use as time goes on and all
new .Net technologies are co-opted toward C# ( and VB .Net ), despite
C++/CLI''s superiority other .Net languages.

>C++/CLI is such a good language, with so much careful and intelligent

>decisions made so that it is superior to C# in almost every way, that it
is sad to finally realize that Microsoft never had any plans for C++
developers to effectively compete with C# developers in the .Net world.

I agree, C++/CLI is a way better language than C# - and I could never
truly understand why Microsoft gave themselves the headache of
supporting 3 general purpose languages when 1 could have done it all.
IMHO they made lots of poor decisions with .Net - but it''s all water
under the bridge now - isn''t it?

At least we know they now know that people use C++ for developing all
aspects of Windows applications in the native code area - let''s just
hope they don''t forget that!

Dave

这篇关于VS2008中VC ++ .Net中的失望的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！