Re: I have 2 versions of .NET, which is being used
- From: "Richard Grimes" <richardg@xxxxxxxx>
- Date: Mon, 2 Jan 2006 12:06:10 -0000
Scott M. wrote:
> applications written for .NET. And, by the way, in my first reply I
> also said that I don't believe it would happen as soon as Vista
> becomes available, it will take time for Vista to be the predominant
> OS out there.
Many people are asking 'why should I upgrade to Vista'? You don't need
to upgrade to get WinFX (and the advantages of WPF and WCF - Avalon and
Indigo) so why not stay with XP? I guess the main 'upgrade' route will
be through new machines, because Microsoft will mandate that new Windows
machines will be Vista. So, as you say, it may take a long time for
Vista to be predominant.
> Microsoft has not abandoned new .NET applications at all. Where did
> you get that from?
By looking at how many .NET applications Microsoft is producing, and how
much .NET there is in Vista. Vista may have .NET 2.0, but it does not
have WinFX. We are told that WPF and WCF will revolutionize the way that
applications will be written, but Microsoft are not using those
technologies themselves. What does that say to you? To me that says that
there are two camps in Microsoft - those pushing .NET and those
resisting it. The former were in charge at the time of the PDC 2003
technical preview of Longhorn, the latter are in charge now.
> Vista [formerly Longhorn] has been in development
> since .NET was. It makes no sense to tear down your next major OS
> just to incorporate your new development platform, just as you won't
> see Office re-written as .NET applications because of the millions of
> lines of non-managed code that is in it.
You have ignored the PDC tech preview of Longhorn. There was a lot of
..NET in that build - a significant portion of the code that accessed
your files was implemented in .NET. In the next public build of
Longhorn/Vista Microsoft quietly removed that stuff.
In any case, a 100% managed OS IMO would be a disaster, because .NET has
not been designed as a framework to write operating systems. However,
you can say the same about Win32. Device driver writers do not use
Win32, they use the DDK which is a totally different API.
> There is no reason at all to believe that *brand new* MS applications
> [again: down the line] won't be written in 100% managed code.
Hmmm, so Microsoft decides that they want some anti-spyware as part of
Windows. What do they do? Well they buy up a product that was written in
unmanaged VB and they port that code. Don't you think that would be a
good opportunity to rewrite the code as managed code? (Heck, they could
even use the VB porting tool that they tell their customers to use <g>).
No, they didn't do that, instead they rewrote it as unmanaged C++. What
does that say?
Richard
--
Fusion Tutorial: http://www.grimes.demon.co.uk/workshops/fusionWS.htm
Security Tutorial:
http://www.grimes.demon.co.uk/workshops/securityWS.htm
.
- Follow-Ups:
- Re: I have 2 versions of .NET, which is being used
- From: Scott M.
- Re: I have 2 versions of .NET, which is being used
- From: Lloyd Dupont
- Re: I have 2 versions of .NET, which is being used
- References:
- Re: I have 2 versions of .NET, which is being used
- From: Richard Grimes
- Re: I have 2 versions of .NET, which is being used
- From: Scott M.
- Re: I have 2 versions of .NET, which is being used
- From: Richard Grimes
- Re: I have 2 versions of .NET, which is being used
- From: Scott M.
- Re: I have 2 versions of .NET, which is being used
- Prev by Date: Re: I have 2 versions of .NET, which is being used
- Next by Date: Re: I have 2 versions of .NET, which is being used
- Previous by thread: Re: I have 2 versions of .NET, which is being used
- Next by thread: Re: I have 2 versions of .NET, which is being used
- Index(es):
Relevant Pages
|
Loading