Re: Why no serious MS Application in .NET yet ??
From: palang (palang_at_discussions.microsoft.com)
Date: 03/09/05
- Next message: palang: "Re: Why no serious MS Application in .NET yet ??"
- Previous message: Mattias Sjögren: "Re: Managed module"
- Maybe in reply to: Markus: "Re: Why no serious MS Application in .NET yet ??"
- Next in thread: alejandro lapeyre: "Re: Why no serious MS Application in .NET yet ??"
- Reply: alejandro lapeyre: "Re: Why no serious MS Application in .NET yet ??"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 9 Mar 2005 15:55:03 -0800
Java tried that route with swing. Look where it got them. Java fist started
with an AWT which used the native OS API directly. Then Sun came out with
swing, which is a pure java implementation of the UI. Have you ever seen what
a swing app looks like? Believe me it’s not something to brag about. Almost
everybody I talk to that is currently using java is switching to SWT which is
once again an API developed using the native OS UI API.
Also,
Why wouldn't Microsoft want to take advantage of the underlying Win32 API?
If the OS shell ever changes (hint Windows XP and themes), the .Net framework
would be consistent out of the box.
Therefore, having the .Net framework utilize the Win32 API will give us a
consistent look and feel. Whereas having a pure managed implementation might
give us a consistent UI but would certainly have to be changed with every
release of the OS and framework version.
That is the beauty of the framework. It allows you to easily interop with
Win32 and COM.
"alejandro lapeyre" wrote:
> That is why I said there is a lot of work to do.
> there is nothing done yet.
>
> regards,
> Alejandro Lapeyre
>
> "Herr Lucifer" <"\n"HerrLucifer\n@microsoft.com> escribió en el mensaje
> news:O5ntJlAHFHA.3092@tk2msftngp13.phx.gbl...
> >
> > "alejandro lapeyre" <alejandrolapeyre@jotmail.com> wrote
> >> The .NET is great, but it needs a lot of work to replace the windows api.
> >> Before asking that Office is written in .NET, the ListBox should be
> >> written in .NET!
> >
> > Replace the API? You're kidding! Dot Net doesn't really do anything on its
> > own. It only calls the unmanegd APIs (built in Win32) from a managed
> > environment. Take a look inside the framework yourslef to see what is
> > really there.
> > Download and use this disassembler: (Reflector)
> > "http://www.aisto.com/roeder/dotnet"
> >
>
>
>
- Next message: palang: "Re: Why no serious MS Application in .NET yet ??"
- Previous message: Mattias Sjögren: "Re: Managed module"
- Maybe in reply to: Markus: "Re: Why no serious MS Application in .NET yet ??"
- Next in thread: alejandro lapeyre: "Re: Why no serious MS Application in .NET yet ??"
- Reply: alejandro lapeyre: "Re: Why no serious MS Application in .NET yet ??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|