Re: I have 2 versions of .NET, which is being used

> Your terminology is misleading, 'native support of .NET' appears to be a
> contradiction since most people use the term 'native' to mean x86 code.

Most people use the term *native code* to mean x86 code, I didn't say
*native code*, I said *native support*. I didn't say that Windows Vista
uses .NET *as* its native code. The term *native* only means that something
is *built-in* or *standard* with something. Just as we can talk about the
*native* data-types of this language or that. When people mean what you
thought I was saying, they'll say *native code* (not native support)
[splitting hairs at this point].

> I understand what you mean now. However, note that Win 2003 Server had
> .NET 1.1 installed from the distribution CD (and hence didn't require an
> windows update), but that did not create a new .NET market.

Because the average consumer doesn't run Win2003 Server.

My point was simply that as .NET becomes *natively available* as part of the
most mainstream OS in the world, you will see more consumer 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.

> Incidentally, the point of my article was that it's my opinion that
> Microsoft have abandomed any intention of writing new code in .NET - the
> new innovations in Vista will *all* be native (ie non-managed) code.

Microsoft has not abandoned new .NET applications at all. Where did you get
that from? 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.

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.

-Scott


.

Relevant Pages

  • Re: "The system cannot execute the specified program."
    ... were indeed DLLs that it needed that the OS couldn't find. ... Are you using Vista? ... network shares in Vista. ... access security' which prevents the running of .Net applications from a ...
    (comp.lang.python)
  • Embeddable databases
    ... database engine for .NET applications. ... Microsoft ... JET is not an option, as it looks like it is being quietly ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: introspection in SML
    ... It is an exaggeration to say "most people have already migrated". ... Microsoft would like everyone to think that, but in fact only a small ... The code base is even smaller. ... Most non-trivial ".NET applications" ...
    (comp.lang.functional)
  • Re: VB6 and .NET
    ... I phoned back Microsoft and although they had a record of my call they ... Now I'm told I can downgrade my licence to VB6. ... The US Microsoft site states that the media is available from them ... They told me I could use VB.Net for non .Net applications as ...
    (microsoft.public.dotnet.general)
  • Re: InnoSetup features
    ... hassle that Inno for Vista. ... It costs money though. ... I think for .NET applications or applications with newer MS ... dependencies MSI makes sense. ...
    (borland.public.delphi.thirdpartytools.general)
Loading