Recently, the WinFX SDK and the Avalon Binaries Beta 1 have been released. However, Xaml files are still opened by Notepad and the nice preview in Internet Explorer is still gone. This is why I decided to update my XamlViewer application which can be used on Windows XP SP2, Server 2003 SP1, Vista, and Server Code Name: “Longhorn” Beta 1.

You can download it from here.

The Internet Explorer team has done great job with the new Internet Explorer 7 Icon and Logo. However, there will be another icon used in Windows Vista™, they say - this one will be used in Windows XP SP2, Server 2003 SP1, and Windows XP x64 only.

The last week, AlphaAlien, y_notm and myself worked on a guide regarding customizing the Windows Search and Indexing Engine experiences. I have coded a little application that loads itself in the background and waits for Windows Search windows or Open/Save file dialogs to appear. It enables the Search button and you are able to search in both indexed and non-indexed custom folders (although, it is recommended that you search in indexed folders only, otherwise the search would take some time). The application is acompanied by a few Command Prompt scripts which allow you to make it run on Start Up automatically, stop it, or remove it from the StartUp folder.

You can get the application here and the guide is available here.

Note: The application is tested in both Windows Vista and Windows Code Name: “Longhorn” Server and works fine. You need .NET Framework, at least v1.1, and v2.0 comes pre-installed with Windows Longhorn.

AlphaAlien, y_notm and myself have been working on a guide to customize the Windows Search Engine experiences in the recent release of Windows Vista Beta 1. The guide covers the following themes: creating custom Virtual Folders (search queries), making the Indexing engine index files in usual folders (not only in the \Users\ one), and the incompleted ‘Custom-location indexed search’ - so far this can be done using a third party handle viewer and manipulator to enable the appropriate combo box; I am working on an application that should do this automatically.

You can read the guide here: HOW TO: Customize search locations in Vista Beta 1.

On the other hand, Nighthawk and myself made a little pack for the Window Desktop Manager that allows it to read per-user settings, so that every user on the computer can have different settings. The package also contains a few Registry key files that allow fast switching of the available features, such as Blurring, Slow Animations when the Shift key is held, Animations and Glass effect. You can download the pack here: Per-User DWM Modification.

The highly anticipated Beta program of Windows® Vista™, formerly known under the code name “Longhorn”, has just started. Bets 1 has been given to first batch of testers for feedback: primarily bug reporting and suggestions. The press kit, which contains official screenshots, too, can be found here.

The highly anticipated Beta 1 of Windows “Longhorn” will be released pretty soon to testers and MSDN subscribers. Subscribers can now even request product key(s) for it.

A little flashback: Windows Code Name: “Longhorn” has been developed for the last 4 years, and Microsoft switched to the Windows Server 2003 SP1 code base in September 2004. Some of the features to be implemented and which are already implemented are:

• Windows Image Deployment Features fast installation and upgrade of Windows OS using a disk image (WIM file) created with the Windows Imaging Utility, also known as xImage, an internal tool that is expected to be released to OEM partners regarding unattended installations.
• Faster Application Starting Using the more advanced ‘Pre-Fetch’, called ‘SuperFetch’.
• New User Experience, and Graphic engine The new User Experience is called Aero, and the shell - AERO. Aero has 4 tiers, which can be enabled depending on the GPU’s capabilities. Aero is bult on Avalon and will use graphics hardware acceleration where available. Requirements are: DirectX 9 GPU, at least 64MB of Video memory, drivers must be designed for the Longhorn logo, i.e. are LDDM compatible. The new graphic engine is called Avalon and is managed code API, built on MIL, for XAML Applications. Avalon graphics are resolution-independent, because they are vector, and this is a pro for users with high-DPI computer screens.

  The AERO shell, which is rumoured to be the project Code Name: “M”, as well as the Aero UX, will debut in Beta 2, which is expected to be released late 2005, or early 2006.

  Aero Glass Support for 3D graphics, animaton transitions and special effects which are made possible by the MIL

  Aero Express Comparing to Aero Glass, the Express tier presents only basic effects for the UI. Amongst the publicly released builds, only 4074.idx2 and 5048.winmain contain Aero Express, although only 5048.winmain has developed LDDM (see below).

  To Go To Go is intented for mobile computers primarily because it doesn’t take much resources, presents no special effects (legacy UX support in Windows Vista).

  Aero Diamond Diamond is a tier intented for the Media Center Edition of Windows Vista.

  The Windows Graphics Foundation draft document, as well as Caps requirements for Aero, can be found here, thanks to funny_bala for the link.

• The Indigo Services Indigo, also known as the Microsoft Message Bus, is a set of services for
• Palladium The Next-Generation Secure Computing Base (NGSCB) which presents the enhanced ways for client data protection and the Digital Rights Management, built in Windows “Longhorn”.
• Longhorn Display Driver Model LDDM allows the visual effects seen on a user’s desktop to scale relative to the available graphics hardware. The Aero Experience will need LDDM compatible drivers for best performance. The XP model, which has been used in Windows since 1996, is still supported in “Longhorn”, though, only for compatibility. 5048.winmain is the only public build to date to contain a workable LDDM, 4074.idx2 has drivers for Intel controllers, but cannot be used.

It is known that Windows Vista will also present the next (11th) version of the Media Player, Office 12 and have built-in support for writing data to DVD discs. The server version will be out in 2007, having WinFS in it — the new file storage system (not file system) which uses the SQL Server 2005 “Yukon” technology for fast desktop search and file organisation.

–Stanimir

That’s right, according to a beta community, the Beta 1 build of Windows Code Name: “Longhorn” (note that the build won’t be tagged as “Vista”) will be released to testers tomorrow, Wednesday. The number will be about 5112 and MSDN Subscribers are going to be able to get it by the targeted date, August 3rd.

The build’s downloading will be done in stages, in order to preserve the servers from hammering. And people who expect invites for the beta shouldn’t worry, either - thousands of invites are sent each week. Current “pending” testers should get their status changed to ‘Active’ or ‘Approved’ by tomorrow morning.

BTW, Beta 1 of the WinFX SDK and Avalon is going to be released by Microsoft tomorrow, too. You can expect two little articles on both themes here and/or on AeroXperience soon.

It seems that two of the registered Windows® Vista™ domains, http://www.windowsvista.us and http://www.windowsvista.tv, are live. It’s strange, though, that they do not redirect to the Vista home page, but Microsoft’s root page. The .Com, .Net and other domains still do not work.

The folks at Mobiform seem to be working on a XAML editor called “Aurora”. It supports the latest (Beta 1 RC) release, and I’m sure they will update their application after Jul 27th when WinFX SDK and Avalon Beta1 should be released to MSDN Subscribers.

Anyway, Aurora can be seamlessly integrated to Microsoft Visual Studio 2005 and developers easily design their XAML controls, forms and so on, used in Avalon (Navigation) Applications. If you’re a XAML enthusiast, you can get the free BETA of Aurora from Mobiform’s web-site.