.NET是否取代Win32？ [英] Is .NET to replace Win32?
问题描述
我还是.NET的新手，来自win32背景。
我很高兴我在.NET中看到的虽然它有点慢比
我想要。它也有一个很好的oo设计，C＃是一种很棒的语言
可以写入。
但它的设计就像是一个更新/更好的MFC永远都会在win32或类似的东西上休息
？或者.NET会接管
编写Windows软件的方法吗？
谢谢。
除了某些东西，绝对要......（但这需要时间）
方式？这取决于你。
Phill，
现在，它通常位于Win32之上它是
的功能（例如，System.Windows.Forms中的类
名称空间）。但是，阿瓦隆会改变这一点。 Avalon的代码库是
托管代码（就像Indigo和WinFx一样），并且没有非托管代码
接口。如果非托管代码想要连接到这些东西，那么它将需要为托管代码获取一个非托管代码包装器。
这不是意味着Win32平台的进步不会占据
的地方。例如，NTFS即将到来的事实
交易。有一个Win32入口点用于开始/结束
交易，并且可能还有一个托管入口点。
希望这会有所帮助。 />
-
- Nicholas Paldino [.NET / C＃MVP]
- mv*@spam.guard.caspershouse.com
" Phill" < WA ******** @ yahoo.com>在消息中写道
新闻：ac ************************* @ posting.google.co m ... < blockquote class =post_quotes>我还是.NET的新手，来自win32背景。
我很高兴我在.NET中看到的虽然它有点慢而不是我想要的。它也有一个很好的oo设计，C＃是一种很棒的语言可以写入。
但它的设计就像是一个更新/更好的MFC，它总是会依赖它win32的顶部或类似的东西？或者.NET会接管编写Windows软件的方式吗？
谢谢。
Nicholas Paldino [.NET / C＃MVP]" < mv*@spam.guard.caspershouse.com>写在
消息新闻：OQ ************** @ TK2MSFTNGP11.phx.gbl ...Phill，
现在，它通常依赖于Win32的一些功能（例如，System.Windows.Forms
命名空间中的类）。但是，阿瓦隆会改变这一点。 Avalon的代码库是
托管代码（就像Indigo和WinFx一样），并且没有非托管代码
接口。如果非托管代码想要连接到这些东西，那么它将必须获得托管代码的非托管代码包装。
Nicholas，
不确定从哪里得到这个？ Indigo依赖于COM interop for
bootstrapping，并且通过COM interop，它使得非托管代码可以作为WS-x服务公开，并且可以通过相同的方式从
非托管代码。 Indigo也依赖于Win32的OS服务和需要
非托管组件作为托管服务（http.sys或asp.net）。
Willy 。
I''m still new to .NET and come from a win32 background.
I''m happy w/ what I see in .NET although it is a little slower than
I''d like. It also has a nice oo design and C# is a wonderful language
to write in.
But is this designed to be like a newer/better MFC that will always
rest on top of win32 or something like it? Or will .NET take over as
THE WAY to write Windows software?
Thanks.
On top of something, definitely until ... (but that takes time)
The way? That''s up to you.
Phill,
Right now, it generally rests on top of Win32 for some of it''s
functionality (for example, the classes in the System.Windows.Forms
namespace). However, Avalon will change that. The codebase for Avalon is
managed code (as is Indigo and WinFx), and there will be no unmanaged code
interface. If unmanaged code wants to connect to these things, then it will
have to get an unmanaged code wrapper for the managed code.
This doesn''t mean that advancements in the Win32 platform won''t take
place. Take for example the fact that NTFS is going to be come
transactional. There is a Win32 entry point for beginning/ending the
transaction, and will probably have a managed entry point as well.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Phill" <wa********@yahoo.com> wrote in message
news:ac*************************@posting.google.co m...I''m still new to .NET and come from a win32 background.
I''m happy w/ what I see in .NET although it is a little slower than
I''d like. It also has a nice oo design and C# is a wonderful language
to write in.
But is this designed to be like a newer/better MFC that will always
rest on top of win32 or something like it? Or will .NET take over as
THE WAY to write Windows software?
Thanks.
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:OQ**************@TK2MSFTNGP11.phx.gbl...Phill,
Right now, it generally rests on top of Win32 for some of it''s
functionality (for example, the classes in the System.Windows.Forms
namespace). However, Avalon will change that. The codebase for Avalon is
managed code (as is Indigo and WinFx), and there will be no unmanaged code
interface. If unmanaged code wants to connect to these things, then it
will have to get an unmanaged code wrapper for the managed code.
Nicholas,
Not sure where you get this from? Indigo relies on COM interop for
bootstrapping, and through COM interop it enables unmanaged code to be
exposed as WS-x services and by the same way services can be consumed from
unmanaged code. Indigo also relies on Win32 for it''s OS services and needs
unmanaged components as hosting services (http.sys or asp.net).
Willy.
这篇关于.NET是否取代Win32？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
