It's been a busy week

Coming back from two weeks of vacation, even with a mandatory shutdown between Christmas and New Year's Day, tasks piled up and the week was hectic. The new QA manager is floundering (she already has all her staff alienated), outsourcing our current system software to the China team continues (yes, this doesn't bode well), and the firefighting and political infighting continue. On the positive side, life outside of work is good and my autodidacticism continues as I work through ATL, WTL, and yes, even MFC (the Visual Studio 2008 vintage).

My new Studio 17 notebook was sent back to Dell because IT ordered it with a Blu-ray drive (raising the price $150) and integrated video (saving $150), yielding a lackluster 3.1 on the Windows Experience Index:

There are some things about this machine I do not like, primarily the touchpad and keyboard:

• the keyboard includes a numeric keypad, something I never use
• the and keys and the and keys are all side by side instead of stacked as they should be
• the touchpad is from Alps and it doesn't work as smoothly as a Synaptics touchpad.
• the Menu key is missing from the keyboard, and it's something I use occasionally
• the Windows key sticks when you do E to bring up Explorer, for example: the moment you type an L, you lock the machine. This doesn't happen with an external keyboard, and I'm holding out hope Dell will fix it in an update: I can live with it for now (and complain on the Dell support boards).

However, the display is big and beautiful, the system is fast (even with a 5400 RPM drive, which I'll shortly replace with a 7200 RPM drive), and there's room for a second internal hard drive (that's where the original 5400 RPM drive will go, probably to hold extra or backup VMs, other backups, and maybe a test partition for Windows 7 builds).

Since I got this thing to run Windows 7, do WPF development, and drive an external 1920x1200 monitor (and I'll be stuck with it for some time), I had IT exchange it for one with a regular DVD burner and dedicated graphics ($150). If they had bought me a refurbished MacBook Pro as I originally requested, it would have cost about the same and been faster (albeit with a smaller main screen). This all would have been simpler (and faster) if I had been given a budget and allowed to create the order myself.

In other news, my former employer in Tampa is doing gangbusters: two acquisitions in 30 days in a bad recession. I regret burning that bridge: whatever problems there were in product management pale in comparison to the insanity at my current job, but my scorpion nature wasn't quite kept in check when I was there. That, and I should never have taken the QA manager position. C'est la vie...

But hey, at least I have a job, for now. In 9 days, the country is officially under new management, and I am hopeful President Obama will make the right decisions and form the right alliances and help set this nation on a course to realizing our potential. If nothing else, he can't possibly do worse than the idiots we've had running things for the last 8 years (last 28 years, actually).

More WTL resources

Using the Windows Template Library articles by R. Mack

• Part 1: Getting Started
• Part 2: Windowing

After a promising start which builds from an empty WinMain(), it peters out after a couple of examples. Still, it's worth reading to see how simple it is to start pulling in WTL bits.


WTL Makes UI Programming a Joy articles (Zip files with a Word doc and zipped source) by Chris Sells, Dharma Shukla, and Nenad Stefanovic

• Part 1: The Basics
• Part 2: The Bells and Whistles

Stefanovic is the creator of WTL, and while dated, these articles are worth reading to get a little deeper into WTL.


A page of WTL links in the Philippines which includes Eamon Tuathail's humbling WTL Developer's Guide in PDF: highly recommended.


Finally, a WTL tip: if you're like me, you build with Warning Level set to Level 4 (/W4) and with Treat Warnings As Errors set to Yes (/WX). To get rid of those C4996 warnings, define _SECURE_ATL.

Getting started with WTL

I've spent the holidays (re)learning about WTL, so I thought I'd make a few notes as I went.

I'm using Visual Studio 2008 Professional on Vista SP1, so if you're using something else, the details may be slightly different. The essentials will be the same, though.

The first step is to make sure you have WTL on your machine with the App Wizard registered.

The current version of WTL is 8.0, and it can be found on SourceForge, oddly enough. Just download the Zip version and extract the contents into a folder on your system (I used C:\WTL80).

WTL comes with a number of scripts to add WTL support to the App Wizard in Visual Studio, but 8.0 was released before Visual Studio 2008 came out, so you'll have to add the WTL support yourself. Fortunately, it's incredibly simple:

• copy AppWiz\setup80.js to AppWiz\setup90.js
• open setup90.js in a text editor and make the following changes:

Compare: (<)C:\WTL80\AppWiz\setup90.js (6399 bytes) with: (>)C:\WTL80\AppWiz\setup80.js (6401 bytes)

12c12
< // Setup program for the WTL App Wizard for VC++ 9.0 (Orcas) --- > // Setup program for the WTL App Wizard for VC++ 8.0 (Whidbey)
72,73c72,73
< strvc9key = "HKLM\\Software\\Microsoft\\VisualStudio\\9.0\\Setup\\VC\\ProductDir" strvalue =" WSShell.RegRead(strVC9Key);"> var strVC8Key = "HKLM\\Software\\Microsoft\\VisualStudio\\8.0\\Setup\\VC\\ProductDir";
> strValue = WSShell.RegRead(strVC8Key);
79,80c79,80
< strvc9key_x64 = "HKLM\\Software\\Wow6432Node\\Microsoft\\VisualStudio\\9.0\\Setup\\VC\\ProductDir" strvalue =" WSShell.RegRead(strVC9Key_x64);"> var strVC8Key_x64 = "HKLM\\Software\\Wow6432Node\\Microsoft\\VisualStudio\\8.0\\Setup\\VC\\ProductDir";
> strValue = WSShell.RegRead(strVC8Key_x64);
84c84
<> WScript.Echo("ERROR: Cannot find where Visual Studio 8.0 is installed.");
144,146c144,146
< strline = "Param=\" wizard_version =" 9.0\"> strLine += ".8.0";
> else if(strLine.indexOf("WIZARD_VERSION") != -1)
> strLine = "Param=\"WIZARD_VERSION = 8.0\"";

You only need to change all 8.0 instances to 9.0; all the other changes are ones I made to productize the script, because that's how I roll.

Anyway, shut down Visual Studio 2008 if you have it running, run setup90.js, start Visual Studio 2008, and create a new project.

You will now see a WTL node under Other Languages\Visual C++, right below Win32:


Go ahead and create a scratch project using the wizard and take a look at the code. WTL comes with a dozen samples, including some for Vista, so be sure to take a look at them as well.

When you're ready to continue, head over to the excellent series of WTL articles on CodeProject, starting with Michael Dunn's WTL for MFC Programmers series.