为什么没有用.NET构建MS产品？ [英] Why no MS products built with .NET?
问题描述
我正在读另一本关于.NET的书 - VB 2005 Professional（wrox）和
阅读声明;
" Microsoft已经赌了他们的.NET上的未来并公开声明
从此几乎所有的研发工作都将在这个
平台上完成。预计最终几乎所有的微软产品都会被移植到.NET平台上。
所以我想到了这个声明分钟 - 然后我意识到我有所有微软的产品，而不是一个使用.NET框架的产品。我认为你可以找出一个显而易见的问题 - 为什么不呢？持续6年
of .NET现在，这些Microsoft .NET迁移产品在哪里？ MS Office
当然不是 - 当我安装了
时，它不需要我安装.NET框架（在非.NET机器上） ，也不是很多其他主流的微软
产品。
这是另一种情况按照我说的做，不像我做的那样？或者移植到
..NET平台比他们想象的要困难得多？或者它是更多的b $ b bominious，.NET什么都没有准备好黄金时间（当然
不是零售）。
Rob。
Rob R. Ainscough写道：我正在阅读另一本书。 NET - VB 2005 Professional（wrox）
并阅读声明;
所以我想了一下这句话 - 然后我意识到
我有所有的微软'' s产品
真的全部？我打赌不是......
而不是一个人使用.NET
框架。
你没有得到好的:-)
例如，许多使用SharePoint的服务器端工具都是
至少部分编写在ASP.NET中。
Visual Studio本身部分用.NET编写，Team Services也是如此。
我想你可以找出一个显而易见的问题 - 为什么<不是吗？现在已经有6年的.NET了，这些Microsoft .NET
迁移产品在哪里？ MS Office当然不是 - 当我安装.NET框架（在非.NET
机器上）时，它并不需要我安装.NET框架，也不是许多其他主流Microsoft产品。
Geee ... Office是一个数百万行的源代码库，在.NET发明之前编写，测试过
并且是合格的。在.NET中重写它需要花费多少年人（可能甚至几百年人）？
对最终用户来说绝对没有任何好处。你必须考虑新的
产品，当然不是历史产品。
Arnaud
MVP - VC
>我有所有微软的产品
你真的拥有微软的所有300个软件产品，或者你是否b / b $ b认为所有的微软产品都包括Office ，Windows和VS？
" Rob R. Ainscough" < RO ***** @ pacbell.net>在消息中写道
新闻：OM ************** @ TK2MSFTNGP10.phx.gbl ...我正在读另一个关于.NET的书 - VB 2005 Professional（wrox）和
阅读声明;
微软已经将自己的未来放在.NET上并公开表示
从此几乎所有他们的研究和开发将在这个平台上完成。预计最终几乎所有的微软产品都将移植到.NET平台上。
所以我想了一下这句话 - 然后我意识到我
拥有所有Microsoft的产品，而不是一个使用.NET框架的产品。我想你可以找出一个显而易见的问题 - 为什么不呢？现在继续使用6年的.NET，这些Microsoft .NET迁移产品在哪里？ MS
办公室当然不是 - 我安装.NET框架时不需要我安装它（在非.NET机器上），也不是很多其他的主流微软产品。
这是另一个案例按照我说的做，不像我做的那样？或者移植到.NET平台比他们想象的要困难得多？或者它是更有魅力的.NET，任何事情都没有真正为黄金时间做好准备（当然不是零售）。
Rob。
是的，我确实拥有它们。但是真的，我还没有测试过每一个，但是肯定没有他们的主流产品是写的或者没有使用
托管或非托管的.NET框架。如果您知道他们的主流
产品，请告诉我。如上所述，这里和那里出现了一些低价的b $ b配置文件工具，但当然没有什么我会考虑的素数
时间。
我刚才引用了这本书，这本书正在转发微软出售给
社区的内容。我意识到这可能是这本书的销售宣传，以便让人觉得对.NET的投资是值得的 - 但无论如何，你是
转移问题：
黄金时间在哪里？ .NET产品？微软希望/希望每个人都能移民，所以为什么不是微软？而且我不会认为微软是唯一一家拥有数百万行零售产品代码的公司 -
信不信由你，其他公司都有产品还有数百万的b $ b行代码 - 如果从头开始重写它们需要6年时间
或将它们迁移到.NET然后我会建议那是不是好消息。
但问题仍然存在，为什么没有来自.NET的
创建者的基于.NET的黄金时段产品？
我的意思是我们现在已经进入.NET 6年了，所以我会期待一些东西 - 甚至MS Money
2006不是基于.NET的（相对简单零售的产品
I was reading yet another book on .NET - VB 2005 Professional (wrox) and
read the statement;
"Microsoft has staked their future on .NET and publicly stated that
henceforth almost all their research and development will be done on this
platform. It is expected that, eventually, almost all Microsoft products
will be ported to the .NET platform."
So I thought about this statement for a minute -- then I realized that I
have ALL Microsoft''s products and not a single one uses .NET framework. I
think you can figure out the obvious question -- why not? Going on 6 years
of .NET now, where are these Microsoft .NET migrated products? MS Office
certainly isn''t -- it doesn''t require me to install .NET framework when I
installed it (on a non-.NET machine), nor many other mainstream Microsoft
products.
Is this yet another case of "do as I say, not as I do"? Or was porting to
..NET platform a lot more difficult than they thought? Or is it the more
ominious, .NET anything just isn''t really ready for prime time (certainly
not retail anyway).
Rob.
Rob R. Ainscough wrote:I was reading yet another book on .NET - VB 2005 Professional (wrox)
and read the statement;
So I thought about this statement for a minute -- then I realized
that I have ALL Microsoft''s products Really all? I bet not...
and not a single one uses .NET
framework. You do not have got the good ones :-)
Many server side tools working with and above SharePoint, for example, are
written at least in part in ASP.NET.
Visual Studio itself is written in part in .NET, as is Team Services.
I think you can figure out the obvious question -- why
not? Going on 6 years of .NET now, where are these Microsoft .NET
migrated products? MS Office certainly isn''t -- it doesn''t require
me to install .NET framework when I installed it (on a non-.NET
machine), nor many other mainstream Microsoft products.
Geee... Office is a multi-million lines source base that was written, tested
and qualified before .NET was invented. What would be the point to spend
many years-man (probablty even centuries-man) to rewrite it in .NET? There
will be strictly no benefit for the end-user. You must think about new
products of course, not historical ones.
Arnaud
MVP - VC
> I have ALL Microsoft''s products
Do you really have all the 300 software products from Microsoft, or do you
think that ALL microsoft products include Office, Windows and VS?
"Rob R. Ainscough" <ro*****@pacbell.net> wrote in message
news:OM**************@TK2MSFTNGP10.phx.gbl...I was reading yet another book on .NET - VB 2005 Professional (wrox) and
read the statement;
"Microsoft has staked their future on .NET and publicly stated that
henceforth almost all their research and development will be done on this
platform. It is expected that, eventually, almost all Microsoft products
will be ported to the .NET platform."
So I thought about this statement for a minute -- then I realized that I
have ALL Microsoft''s products and not a single one uses .NET framework. I
think you can figure out the obvious question -- why not? Going on 6
years of .NET now, where are these Microsoft .NET migrated products? MS
Office certainly isn''t -- it doesn''t require me to install .NET framework
when I installed it (on a non-.NET machine), nor many other mainstream
Microsoft products.
Is this yet another case of "do as I say, not as I do"? Or was porting to
.NET platform a lot more difficult than they thought? Or is it the more
ominious, .NET anything just isn''t really ready for prime time (certainly
not retail anyway).
Rob.
Yes I do have them all. But true, I haven''t tested EVERY SINGLE one yet,
but certainly none of their main stream producst are written or make use of
managed or unmanaged .NET framework. If you know any of their main stream
products that are, please let me know. As mentioned it appears a few low
profile tools here and there, but certainly nothing I''d consider "prime
time".
I was just quoting the book, which was relaying what Microsoft sold to the
community. I realize it is perhaps a sales pitch for the book so as to make
one feel the investment in .NET is worth it -- but regardless, you''re
diverting from the issue:
Where are the "prime time" .NET products? Microsoft expect/hope everyone
migrates so why aren''t Microsoft? And I would NOT assume that Microsoft are
the only company with millions of lines of code for a retail product --
believe it or not, other companies exist that have products with millions of
lines of code also -- and if it takes 6 years to rewrite them from scratch
or migrate them to .NET then I''d suggest that is NOT good news.
But the question remains, why no prime time products based on .NET from the
creators of .NET?
I mean we''re 6 years into .NET now, so I''d expect something -- even MS Money
2006 is not .NET based (a relatively simple product that retails for
这篇关于为什么没有用.NET构建MS产品？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
