Recommended Posts

First part of a series of guides for the main features of Longhorn here at Neowin for those wanting to know more about specific technologies included in Microsoft Windows Code Name "Longhorn"

What is Avalon?

Avalon is the next-generation platform for Windows client applications. It combines the best features of the Web such as ease of deployment and rich mix of application and content with the power of the Win32 development platform to enable developers to build a new breed of applications that are robust and take real advantage of the connectivity, storage, and graphical capabilities of the modern PC. Avalon is not just about User Interface and Rich Graphics, although that is an important part, the overarching goal of Avalon is that it offer a common managed code exposure to all the capabilities of the Personal Computer including storage, communications, documents, multimedia etc.

Will Avalon applications work much like Win32 applications?

They could, but Avalon will offer a number of features that will make them work much better. Avalon applications take advantage of a variety of services, including an efficient storage mechanism for application code and documents, and automatic persistence of the application state.

What will Avalon offer that we can?t get from .NET?b>

Avalon should be viewed as a powerful set of client side technologies that enable .NET to truly exploit the power of the smart client. It provides services ranging from local storage, to graphics and multimedia, to connectivity, in order to enrich the user experience and provide interactive, media rich applications.

What will the Avalon presentation layer look like?b>

In terms of our current OS, Avalon will provide a replacement for the presentation layer that is currently provided by Internet Explorer/Trident, User, GDI+, and Cicero. Avalon will also be closely integrated with parts of the Shell for Longhorn and even more so for versions of Windows after that.

What kind of graphics support will Avalon provide?b>

It will take advantage of the merged graphics functionality of GDI+ and DirectX, as well as the Media Framework from the Digital Media Division as well as providing a rich vector based format with support for SVG markup language.How will Avalon handle networking support?b>

Avalon will provide all the support needed to create a fully connected client application. In the short-term, WinHTTP will replace WinInet. In the long-term, Avalon will provide support for a variety of networking services, including peer-to-peer networking, consumption of Web Services, and Hailstorm/Rainstorm.

What will Avalon provide for data services?b>

Avalon will expose the new Windows storage functionality available in Longhorn. Built on SQL technology this will allow us to provide online and offline storage, a powerful data binding model and a collection of data oriented controls.

Avalon is the platform for the next-generation of Microsoft? Windows? client applications. It will create a new presentation platform by combining the best features of the Dynamic HTML (DHTML) and Win32 development platforms. Avalon will support the transition from stand-alone client applications to connected Microsoft? .NET applications.

Avalon intends to re-energize Windows as a platform for developing client applications. Currently, .NET is heavily server-oriented with the client-side user interface largely limited to HTML 3.2. Avalon extends the Microsoft .NET strategy to include the client and differentiate Windows. Avalon will enable developers to combine the rich end-user experience of a Win32 application with the power of server-based .NET servicWhat is Aero??

Aero is the new Windows user experience. Aero consists of guidelines, recommendations, and user experience values that help developers applications get the most out of the Microsoft? Windows? Code Name "Longhorn" pillars: rich presentation (Code Name "Avalon"), data (Code Name "WinFS"), and communication (Code Name "Indigo").

Link to comment
https://www.neowin.net/forum/topic/111675-what-is-avalonaero/
Share on other sites

Not sure if I'm making sense... but I wonder if someone could give a Win9x/2k/XP equivalent (term/name) of Avalon / Aero, if any? Some familiar term might allow us to understand it much more easily than reading a paragraph of explanations / descriptions of (new) concepts? :)

But anyway, thanks lots to creamhackered for the time/effort put into giving us such detailed information!

  • 3 weeks later...

Avalon is just the presentation layer, not the API. This is a common misconception. WinFX is the new Windows API. Both are written in managed code. A lot of people are also confusing (including one Microsoft person) that WinFS is storage and WinFX is the new API.

  • 3 weeks later...
  • 1 month later...
Avalon is just the presentation layer, not the API. This is a common misconception. WinFX is the new Windows API. Both are written in managed code. A lot of people are also confusing (including one Microsoft person) that WinFS is storage and WinFX is the new API.

hehe - WinFX is that stardock program - will we see a law case here?

  • 2 weeks later...
  • 3 weeks later...
  • 1 month later...
  • 2 weeks later...
  • 2 months later...

Avalon is designed to replace Explorer.exe and IExplore.exe as the main shell.

Avalon is a CLR based desktop graphics runtime environments and is optimized to render vectors very fast (it's realtime DX rendering), so expect see lot's of this kind of stuff in LH. Writing an application to use Avalon requires the use of WinFX as this is the API as pointed out earlier in the thread

Avalon is designed to replace Explorer.exe and IExplore.exe as the main shell.

Avalon is a CLR based desktop graphics runtime environments and is optimized to render vectors very fast (it's realtime DX rendering), so expect see lot's of this kind of stuff in LH. Writing an application to use Avalon requires the use of WinFX as this is the API as pointed out earlier in the thread

While Avalon is being touted as both an Explorer and IE replacement, IE has pretty much eaten Windows Explorer (case in point, the fact that you can *still* open Web pages with *Windows Explorer*, in addition to IE). Avalon is the closest approach to a *very* early Microsoft-demoed technology that I called *Explore Everything* back in the Windows 95 days (and it was in the leaked *Nashville* and Nashville II* builds). The difference between IE/Explorer then and Avalon today is that some funcionality (example: USENET and similar discussion groupage) is deliberately un-explorable via either Explorer or IE (and it was explorable in Nashville and Nashville II). Also, Avalon uses Direct3D and DirectDraw, while the Nashville-based Explorer/IE was entirely DirectDraw-based.

*Nashville* and *Nashville II* were early MS attempts at a more object-oriented OS (not only highly OO, but very HTML-centric as well). The closest approach today to what Nashville/Nashville tried to do is, surprisingly, GNOME on Linux, Solaris, and the BSDs..

  • 4 weeks later...
  • 5 months later...
  • 4 weeks later...
  • 2 weeks later...
  • 3 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!