Holy cow, I wrote a book!
For the story of
how WiX got its name,
I defer to its author,
One "optimization" I've seen from some programs is to defer a bunch
of system configuration work to the first time the program is run
or the first time a feature is requested
instead of doing it at install time.
The problem with this is that the first person to run your program
is not guaranteed to be an administrator.
For example, there is one popular media program that doesn't
install its CD AutoPlay handler until you run it for the first time.
If the first person to run the program is not an administrator,
then their AutoPlay handler doesn't get installed and consequently
This problem became more acute in Windows Vista,
where users do not flex their administrative rights by default,
even if they are administrators.
when run on Windows Vista,
this program never installs its AutoPlay handler.
It fell to the
application compatibility folks to see what
they could do to rescue this program from the
"not compatible with Windows Vista" pile.
It's frustrating having to "fix" something
that was broken when you got there.
Some suggestion box topics turn into daily entries.
Others deserve just a sentence or two.
Here are the short answers.
They take many forms, depending on the situation,
but checking a window caption is definitely ill-advised,
since that creates the opportunity both for false positives
(what if an unrelated program happens to have the same caption?)
and false negatives (will the German version of the program have
the same caption?).
On a related note,
the shim proces itself,
which you might find interesting.
Actually, it does.
What the documentation is trying to say is that
it doesn't work is for things like \\server.
That will return FALSE even if the server exists.
(I've sent a clarification to the documentation team.
Who knows whether they'll accept it.)
This wasn't a topic suggestion, just somebody who wanted to
take what I said and argue against it with made-up facts.
"I to enjoy people that display their ignorance in frount of all of us."
You can get a mirror at Ikea for just a few dollars.
One of the window manager's design principles is that the active
window comes to the top.
Um, I didn't see a topic suggestion in there.
(Not that I really had much incentive to look hard for one.)
It looks like just a bunch of ranting.
If you set your owner correctly and don't play weird games,
everything will be just fine.
The problem is that the taskbar has to play weird games
because of all the other applications that play even weirder
When you play weird games, things get weird.
You can try to fake it but you're going to run into problems.
I don't know but I can guess, and so can you.
Hint: Component layering.
Low-level components vs. higher-level components.
That's a coding style issue.
Believe it or not, different people have different styles,
and there is no mandated "MSDN coding style".
Some people are more averse to the goto statement than others.
Somthing is horribly wrong with your program design if each
edit control in your dialog has its own message pump!
Fix that first, then the tab stop issue should fix itself.
I covered this in
my PDC 2005 talk.
Another category is people who ask a question I've already answered
or ask a question that has already been asked.
I already discussed
the feature process.
I happen to know the person responsible for Start menu and taskbar
features in Windows Vista.
The list of design changes and feature requests
was over 200 items long and obviously not all of them
could be addressed.
(And that list was just of the design changes and feature requests
that overcame the starting point of
minus 100 points.)
This question was asked
over two years after I answered it.
What's particularly baffling about this one is that the time zone
article is one of the most frequently-linked entries I've written!
How could the person not have found it?
I answered this
over a year previously
and then again
three months before the suggestion was posted.
I answered this
over two years previously.
And then there are the people who ask questions on things that I explicitly
listed as topics I am not inclined to cover.
And then there are the suggestions that are so wildly off topic I don't
even know why they bothered to ask me,
this person who wants me to discuss a VB6 language feature
who wants me to discuss non-short-circuit evaluation in Visual Basic.
I have no idea why they chose me to ask these questions.
In my experience, VB doesn't even stand for Visual Basic!
Another person asked
a long, rambling question about Unicode IME that I got tired of reading.
I'm kind of baffled by
this comment asking how to post a comment.
Other topics I am unlikely to cover are
personal biography since that just leads to WikiStalking.
the same question
It duplicates effort.
The ideal length for a topic suggestion is a single paragraph
between two to four sentences.
If it's too short, there isn't enough context.
If it's too long, I will lose interest and not bother reading the suggestion.
That's all the short answers for this year.
(You may have noticed that I've generally been using Mondays
to following up on topics posted to the suggestion box or
in blog comments.)