Re: .NET

From: Alisdair Meredith (alisdair.meredith_at_no-spam-splease@uk.renaultf1.com)
Date: 07/24/04


Date: 24 Jul 2004 00:37:06 -0700

Holger Flick wrote:

> Thank you, Craig.
>
> But what else is there? I looked up Avalon and just found a .NET
> implementation Apache-implementation. What will replace Windows Forms
> then?

Avalon in the MS codename for the GUI/presentation layer and Shell for
Longhorn, the next version of Windows and first to be based on .NET
technology. This will be build around a new XML dialect, XAML, and
will be the preferred way of writing GUIs (not just forms) on that
operating system.

WinForms, and Win32 for that matter, should still work, but XAML will
be the blessed, optimised way of working and where all new features
will show up.

As Craig says though, Longhorn is not due for a couple more years yet,
even without deadline slippage.

AlisdairM(TeamB)



Relevant Pages

  • Re: Does VCL have a future?
    ... Avalon is tied to Longhorn. ... XAML) then you're cutting Windows XP, W2000, etc, out of the equation. ... I think my key point was that the additional Avalon controls are ...
    (borland.public.delphi.non-technical)
  • Re: Allen Bauer on Avalonīs XAML
    ... XAML forms will be released as part of "Longhorn". ... WinForms can run on most earlier versions of Windows ... But "Avalon" will ONLY run on "Longhorn". ...
    (borland.public.delphi.non-technical)
  • WinFX -- The Successor to .NET
    ... Never heard of Avalon? ... these are the WinFX newgroups. ... the next generation set of API's for Windows codename 'Longhorn'. ... You can even make console applications using only XAML. ...
    (microsoft.public.dotnet.general)
  • Re: my doubt that the winform now and the xaml futhure ?
    ... > and just study the xaml in longhorn? ... Well, Vista isn't out yet, and won't be for a while. ... Avalon is going to be available ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: Unmanaged Visual C++ 2005 questions
    ... > The parts of Avalon that Longhorn relies on are not managed, ... since it's built starting with Windows 2003. ...
    (microsoft.public.dotnet.languages.vc)