WPF - 对WinForms的威胁？ [英] WPF--a threat to WinForms?
问题描述
在这里，我正在学习WinForms，两个月后我才知道有一个
WPF API即将推出。这个WPF是否已经出现，对于WinForms来说是一个威胁
，因为我记住的所有库例程和/或
或者在WinForms中熟悉自己将会消失WPF？我在一个早期版本的C＃中注意到了
，这是非泛型的ArrayList。由通用和模板< based List替换了
，但是这种改变是不是很大的事。
。如果WPF进行了这些微不足道的更改，我可以处理
，否则不会。
我看到WPF使用XML的一些变体来代替二进制序列化，
这不是什么大事，但如果它消除了Wizards
界面的Visual Studio 2008 C＃，使用IntelliSense，我将会是
bummed（我对此表示怀疑）。
WPF还支持C＃吗？我想是的。
任何想法都赞赏。对我来说，作为一个来自C ++
背景的新手，C＃.NET很多只是熟悉
入口点（在哪里放置你的代码和什么是首选类
库函数使用），使用''部分
类''和向导非程序化对象实例化更容易。
在我看来（直觉）ASP.NET会受到更多的影响，因为ASP.NET似乎更像是一个脚本/宏语言/或者不是 -
强类型（没有强大的智能感知，至少在我查看它时几年前就已经过了几美元）。
RL
Windows Presentation Foundation
来自维基百科，免费的百科全书
Windows Presentation Foundation（或WPF），以前代号为
Avalon，是.NET Framework 3.0中的图形子系统（以前名为
） WinFX的） [1]并与XAML直接相关。[2] WPF包含在Windows Vista和Windows Server 2008中的
，也可用于Windows XP Service Pack 2或更高版本以及Windows Server 2003.
.
为构建应用程序提供了一致的编程模型，并且
提供了用户界面和
业务逻辑之间的明确分离。可以在桌面上部署WPF应用程序，也可以在Web浏览器中托管
。它还可以实现丰富的控制，设计和Windows程序可视化方面的开发。它旨在将b $ b统一为一系列应用服务：用户界面，2D和3D
绘图，固定和自适应文档，高级排版，矢量
图形，光栅图形，动画，数据绑定，音频和视频。
虽然WinForms将继续被广泛使用，而且微软已经只创建了几个WPF应用程序，该公司推出了WPF for line-
的商业应用程序。[3]
Microsoft Silverlight是一个基于Web的WPF子集，支持Flash-
类似于具有相同编程模型的web和移动应用程序
作为.NET应用程序。不支持3D功能，但包括XPS和
基于矢量的绘图。
这个WPF还没有出来
是的;很长一段时间 - 它是.NET 3.0的一部分;然而，大多数调查
等表明吸收速度很慢（但是人们越来越流行
.NET UI工作的b $ b）。
，它是对WinForms的威胁，因为我记忆的所有库例程和/或
或者在WinForms中熟悉自己会在WPF中消失吗？
由于没有绑定到旧的Windows API，它有一些优势，
以及可直接与Silverlight等相媲美。但它是一个与windows控件完全不同的模型。
。也就是说，
向用户显示数据的一般概念（以及与用户和数据等交互的b / b $ b）保持不变 - 这只是实现
详细说明了这一点。
我看到WPF使用XML的一些变体来代替二进制序列化，
这不是什么大问题但是如果它消除了Wizards
界面的Visual Studio 2008 C＃，使用IntelliSense，我将会b / b
（我对此表示怀疑）。
嗯，.NET winforms也没有使用太多的二进制序列化 -
设计师使用相对少量的代码生成代码生成resx
binary。
WPF还支持C＃吗？ *我想是这样。
这两个是正交概念 - 但是，你可以通过C＃与WPF进行交互
。
另外在我看来（直觉）ASP.NET会更受WP $ WP $ B $的影响，因为ASP.NET看起来更像是一个脚本/宏语言和/或没有 -
强类型（没有强大的智能感知，至少在我查看它的时候几年前就是
a）。
ASP.NET几乎不会受到WPF的影响*。 ASP.NET是一个服务器 -
方http框架。 BAML提供客户端WPF支持，但仅限于
Windows - 但是，Silverlight是多客户端，并且对于客户端丰富的浏览器应用程序具有大量的b
潜力。与
WPF不太一样，但非常相似，并且设计了智能客户端浏览器应用程序。
介意。
Marc
> *如果WPF进行了这些微不足道的更改，我可以处理
it，否则不会。
神圣的废话，老兄。你在开玩笑吗？走出壁橱。将您的
计算机插入互联网。你好像是那种没有好好应对变化的人，这对于你来说，作为程序员的工作对你来说尤其困难。几年来，WPF已经推出了Vista for
。关于它的API信息至少可以获得
三年。 WinForms可以追溯到7年前，尽管
WinForms库的格式类似于之前几年可用的GUI API。
WPF是用于取代WinForms的技术。你可以使用MS在WinForms上提交错误
，但是他们不会得到修复。未来是WPF。并且
它真的很棒。我已经为WPF编写了一年并且热爱它。 WPF
有一些问题，但WinForms有问题。 WPF有很多设计
的工作。总的来说，我认为它已经很好地结合在了一起。
尽管如此，我保证WinForms API不会很快消失
。
< blockquote class =post_quotes>
我看到WPF使用XML的一些变体来代替二进制序列化
我不知道你在这里说的是什么。嗯，实际上，我认为你在谈论XAML。但是，我认为你在比较
苹果和橙子。
WPF作为VS 2008的一部分包含在内。你试过构建吗？ a你好，
世界！应用？我假设有些人喜欢WPF，但我不在乎
它。您可以像使用winforms一样将控件拖到窗体上。您可以使用VB.Net和C＃编码
。
" raylopez99" < ra ******** @ yahoo.com写信息
新闻：1b ********************** ************ @ i76g2000 hsf.googlegroups.com ...
在这里，我正在学习WinForms，我学习了两个月有一个
即将推出的WPF API。这个WPF是否已经出现，对于WinForms来说是一个威胁
，因为我记住的所有库例程和/或
或者在WinForms中熟悉自己将会消失WPF？我在一个早期版本的C＃中注意到了
，这是非泛型的ArrayList。由通用和模板< based List替换了
，但是这种改变是不是很大的事。
。如果WPF进行了这些微不足道的更改，我可以处理
，否则不会。
我看到WPF使用XML的一些变体来代替二进制序列化，
这不是什么大事，但如果它消除了Wizards
界面的Visual Studio 2008 C＃，使用IntelliSense，我将会是
bummed（我对此表示怀疑）。
WPF还支持C＃吗？我想是的。
任何想法都赞赏。对我来说，作为一个来自C ++
背景的新手，C＃.NET很多只是熟悉
入口点（在哪里放置你的代码和什么是首选类
库函数使用），使用''部分
类''和向导非程序化对象实例化更容易。
在我看来（直觉）ASP.NET会受到更多的影响，因为ASP.NET似乎更像是一个脚本/宏语言/或者不是 -
强类型（没有强大的智能感知，至少在我查看它时几年前就已经过了几美元）。
RL
Windows Presentation Foundation
来自维基百科，免费的百科全书
Windows Presentation Foundation（或WPF），以前代号为
Avalon，是.NET Framework 3.0中的图形子系统（以前为
叫做Win FX）[1]并且与XAML直接相关。[2] WPF包含在Windows Vista和Windows Server 2008中的
，也可用于Windows XP Service Pack 2或更高版本以及Windows Server 2003.
.
为构建应用程序提供了一致的编程模型，并且
提供了用户界面和
业务逻辑之间的明确分离。可以在桌面上部署WPF应用程序，也可以在Web浏览器中托管
。它还可以实现丰富的控制，设计和Windows程序可视化方面的开发。它旨在将b $ b统一为一系列应用服务：用户界面，2D和3D
绘图，固定和自适应文档，高级排版，矢量
图形，光栅图形，动画，数据绑定，音频和视频。
虽然WinForms将继续被广泛使用，而且微软已经只创建了几个WPF应用程序，该公司推出了WPF for line-
的商业应用程序。[3]
Microsoft Silverlight是一个基于Web的WPF子集，支持Flash-
类似于具有相同编程模型的web和移动应用程序
作为.NET应用程序。不支持3D功能，但包括XPS和
基于矢量的绘图。
Here I am learning WinForms and two months into it I learn there''s a
WPF API that is coming out. Is this WPF out yet, and is it a threat
to WinForms, in the sense that all the library routines I memorize and/
or familiarize myself in WinForms will disappear in WPF? I did note
in one early version of C#, the non-generic "ArrayList" was replaced
by the generic and template <based List, but that kind of change is
not a big deal. If WPF makes these trivial changes I can deal with
it, otherwise not.
I see WPF uses some variant of XML in lieu of binary serialization,
which is no biggie, but if it does away with the drag and drop Wizards
interface of Visual Studio 2008 C#, with IntelliSense, I will be
bummed (I doubt it).
Also is C# going to be supported in WPF? I suppose so.
Any thoughts appreciated. Seems to me, as a newbie coming from a C++
background, that C#.NET is a lot of just familiarizing yourself with
entry points (where to put your code and what the preferred class
library functions to use), which is made much easier with the ''partial
classes'' and wizard non-programmic instantiation of objects.
Also it seems to me (intuition) that ASP.NET will be more affected by
WPF, since ASP.NET seems more like a script/macro language and/or not-
strongly typed (no strong IntelliSense, at least when I checked it out
a few years ago).
RL
Windows Presentation Foundation
From Wikipedia, the free encyclopedia
This subsystem is a part of .NET Framework 3.0
The Windows Presentation Foundation (or WPF), formerly code-named
Avalon, is a graphical subsystem in .NET Framework 3.0 (formerly
called WinFX)[1] and is directly related to XAML.[2] WPF is included
with Windows Vista and Windows Server 2008, and is also available for
Windows XP Service Pack 2 or later, and Windows Server 2003. It
provides a consistent programming model for building applications and
provides a clear separation between the user interface and the
business logic. A WPF application can be deployed on the desktop or
hosted in a web browser. It also enables rich control, design, and
development of the visual aspects of Windows programs. It aims to
unify a host of application services: user interface, 2D and 3D
drawing, fixed and adaptive documents, advanced typography, vector
graphics, raster graphics, animation, data binding, audio and video.
Although WinForms will continue to be widely used, and Microsoft has
created only a few WPF applications, the company promotes WPF for line-
of-business applications.[3]
Microsoft Silverlight is a web-based subset of WPF that enables Flash-
like web and mobile applications with the same programming model
as .NET applications. 3D features are not supported, but XPS and
vector-based drawing are included.
Is this WPF out yet
Yes; for a long time - it is part of .NET 3.0; however, most surveys
etc show that uptake has been slow (but ever-increasing in popularity
for .NET UI work).
, and is it a threat to WinForms, in the sense that all the library routines I memorize and/
or familiarize myself in WinForms will disappear in WPF?By not being bound into the old windows API it gets some advantages,
as well as being directly comparable to Silverlight etc. But it is a
completely different model to the windows controls. That said, the
general concepts of displaying data to the user (and interacting with
the user and data etc) remain intact - it is just the implementation
details that change.
I see WPF uses some variant of XML in lieu of binary serialization,
which is no biggie, but if it does away with the drag and drop Wizards
interface of Visual Studio 2008 C#, with IntelliSense, I will be
bummed (I doubt it).Well, .NET winforms don''t use much binary serialization either - the
designer does code generation with a relatively small amount of resx
binary.
Also is C# going to be supported in WPF? *I suppose so.The two are orthogonal concepts - but yes, you can interact with WPF
via C#.
Also it seems to me (intuition) that ASP.NET will be more affected by
WPF, since ASP.NET seems more like a script/macro language and/or not-
strongly typed (no strong IntelliSense, at least when I checked it out
a few years ago).ASP.NET will hardly be *at all* affected by WPF. ASP.NET is a server-
side http framework. BAML offers client-side WPF support, but only on
Windows - however, Silverlight is multi-client and has lots of
potential for client-side rich browser apps. Not quite the same as
WPF, but very similar and designed with smart-client browser apps in
mind.
Marc
>*If WPF makes these trivial changes I can deal withit, otherwise not.Holy crap, dude. Is this a joke? Come out of the closet. Plug your
computer into the internet. You seem like the kind of person who
doesn''t deal with change well, which would make a job as a programmer
particularly difficult for you. WPF has been pushed with Vista for
several years now. API info on it has been available for at least
three years. WinForms goes back 7 years, although the format of the
WinForms library is similar to GUI APIs available years before that.
WPF is the technology intended to replace WinForms. You can file bugs
on WinForms with MS, but they won''t get fixed. The future is WPF. And
it rocks, really. I''ve been coding WPF for a year and loving it. WPF
has some issues, but WinForms has ISSUES. WPF has had a lot of design
work. And overall I think it has come together quite well.
Notwithstanding that, I assure that the WinForms API won''t disappear
any time soon.
I see WPF uses some variant of XML in lieu of binary serializationI have no idea what you are talking about here. Well, actually, I
think you''re talking about XAML. However, I think you''re comparing
apples and oranges.
WPF is included as part of VS 2008. Have you tried to build a "Hello,
world!" application? I assume some people love WPF, but I don''t care for
it. You can drag controls onto the form as with winforms. You can code in
both VB.Net and C#.
"raylopez99" <ra********@yahoo.comwrote in message
news:1b**********************************@i76g2000 hsf.googlegroups.com...Here I am learning WinForms and two months into it I learn there''s a
WPF API that is coming out. Is this WPF out yet, and is it a threat
to WinForms, in the sense that all the library routines I memorize and/
or familiarize myself in WinForms will disappear in WPF? I did note
in one early version of C#, the non-generic "ArrayList" was replaced
by the generic and template <based List, but that kind of change is
not a big deal. If WPF makes these trivial changes I can deal with
it, otherwise not.
I see WPF uses some variant of XML in lieu of binary serialization,
which is no biggie, but if it does away with the drag and drop Wizards
interface of Visual Studio 2008 C#, with IntelliSense, I will be
bummed (I doubt it).
Also is C# going to be supported in WPF? I suppose so.
Any thoughts appreciated. Seems to me, as a newbie coming from a C++
background, that C#.NET is a lot of just familiarizing yourself with
entry points (where to put your code and what the preferred class
library functions to use), which is made much easier with the ''partial
classes'' and wizard non-programmic instantiation of objects.
Also it seems to me (intuition) that ASP.NET will be more affected by
WPF, since ASP.NET seems more like a script/macro language and/or not-
strongly typed (no strong IntelliSense, at least when I checked it out
a few years ago).
RL
Windows Presentation Foundation
From Wikipedia, the free encyclopedia
This subsystem is a part of .NET Framework 3.0
The Windows Presentation Foundation (or WPF), formerly code-named
Avalon, is a graphical subsystem in .NET Framework 3.0 (formerly
called WinFX)[1] and is directly related to XAML.[2] WPF is included
with Windows Vista and Windows Server 2008, and is also available for
Windows XP Service Pack 2 or later, and Windows Server 2003. It
provides a consistent programming model for building applications and
provides a clear separation between the user interface and the
business logic. A WPF application can be deployed on the desktop or
hosted in a web browser. It also enables rich control, design, and
development of the visual aspects of Windows programs. It aims to
unify a host of application services: user interface, 2D and 3D
drawing, fixed and adaptive documents, advanced typography, vector
graphics, raster graphics, animation, data binding, audio and video.
Although WinForms will continue to be widely used, and Microsoft has
created only a few WPF applications, the company promotes WPF for line-
of-business applications.[3]
Microsoft Silverlight is a web-based subset of WPF that enables Flash-
like web and mobile applications with the same programming model
as .NET applications. 3D features are not supported, but XPS and
vector-based drawing are included.
这篇关于WPF - 对WinForms的威胁？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
