[Cross-posted in the Code section]

The archive contains classes that can be used to enumerate and/or find windows using their titles, class names or handles.

The Helper.GetWindows() function takes one parameter, a window expression string, representing the window or controls’ hierarchy. For instance,

*[@c=IEFrame]/*[@c=WorkerW]/*[@c=ReBarWindow32]/*[@c=ComboBoxEx32]

can be used to obtain all Internet Explorer (6.*) windows’ URLs.

Extended usage is available in the “Expressions (Usage).txt” file.

Code is compatible with both .NET Framework v1.* and v2.0; however, the sample solution file is created using Microsoft Visual Studio 2005.

ToDo’s:

• Implement starting the search from a non-top-level window.
• Implement obtaining handles to all child windows.

The source code, including a sample application, is available here

Build 5308.17,

Enterprise Edition:

Starter Edition:

Now that the February CTP (also refered to as the Enterprise CTP) is out for beta testers, I have taken a bunch of high-resolution screen captures for non-testers to take a look at (or at least, for my personal reference). This is Ultimate edition.

While waiting for the February CTP, it has been confirmed that the chosen build of Windows Vista and Server Code Name: “Longhorn” is 5308, with full build string of 5308.winmain_idx01.060217-2200. Two screenshots have been posted: showing Internet Explorer and Flip 3D. The build itself should be released later today to all Technical Beta Program participants and Technology Adoption Program members.

 Thanks go to Utakz for the exclusive screenshots.

 Update: The build has recently been released to Microsoft Connect, along with an updated Driver and Software Development Kits. Note that the download servers are getting hammered,so the download speeds are not satisfactory for most testers.

Microsoft have published the February CTP of the WinFX Runtime Components - it includes the Windows Presentation Foundation binaries, as well as the ‘Indigo’ assemblies, and of course documentation. Additional Win32 API documentation can be found in the updated version of the Windows SDK (build 5308.9 for those who are interested).

A good friend of mine known as Utakz posted that the February CTP build of Windows Vista and Server Code Name: “Longhorn” is supposed to be 5308.winmain_idx01 (a very recent compile), and should be released by Microsoft tomorrow (Feb 22nd). This particular build has been recompiled more than ten times which would mean that the original code did contain bugs. Microsoft will also publish an updated version to the Windows AIK (Automated Installation Kit) which contains the deployment tools for Windows NT 6.0, including the famous XImage tool for creating, editing, mounting and deploying Windows Images.

According to Utakz, the build will indeed contain the anticipated Windows Sidebar, perhaps updated versions of the Calendar and Digital Library features. (Do note that Windows Sidebar is anticipated by some people, while the others either don’t like it or would like the 4000-era Sidebar back - including myself.)

Hopefully, known drivers and common bugs have been resolved in this new build and testers will be able to continue testing the next version of Microsoft Windows.

Today I added a new section to this blog, Applications & Code Snippets, where you can find code I have published to the web. Currently, there is only one console application added to the section, a ‘crawler’ for Internet Explorer windows’ URLs. I have coded it a while ago, but I have recently shared it at Channel9 since another ‘Niner’ was looking for such an application. I intend to upload sample code every other day so feel free to request any code via the Contact form.

That’s right,

I haven’t posted in this blog for a lot of time, but as you might have already noticed I have bought the domain name stoyanoff.info, so I will try to keep this blog updated as frequently as possible. I would be posting news, thoughts and code snippets for technologies, such as the Windows Presentation Foundation (that is, Avalon), Windows Vista and Server Code Name: “Longhorn”, and programming itself. I might also edit the current WordPress theme a little, so don’t worry if the elements are messy for a bit.

 Thank you for reading this blog, and I hope you enjoy your stay here. Feel free to comment regarding the topics you would like to be discussed and don’t hesitate to contact me via the contact form - I will try to respond as soon as possible.

Yesterday Microsoft surprisingly announced the first BETA of WinFS (compiled on the Aug 15 2005), but it is intended for use in Windows XP with SP2 only. However, it can easily be made to work in Windows Server 2003 and Vista (code name: “Longhorn”). Here are two ways to do it:

1. Get a HEX Editor application.
2. Start en_WinFS_Beta1.exe and it will extract the necessary contents to C:\\winfsbeta1 (by default). When the extraction process is done, you may get an error message on non-WXP SP2 systems - just disregard and close it.
3. Drag C:\\winfsbeta1\\winfs.msi to your HEX editor and go to offset 0×1FE9E.

Now you can choose one of the following:
#1 4. Look at the ASCII pane and replace = 501 with > 500.
#2 4. Look at the ASCII pane and replace 501 with [NTVersion_Major][NTVersion_Minor]. E.g. “501″ for Windows XP, “502″ for Windows Server 2003, “600″ for Windows Vista (fka. “Longhorn”).

5. At offset 0×1FEBC replace byte 0×32 with 0×30.

-Stanimir

WinFS Beta 1 is out for MSDN Subscribers now. Microsoft has started a new, only WinFS-related blog as well.