Actually, I thought I'd done a fairly good job of censoring, considering how pissed off I am.

You're right. It's clearly more important to avoid offending CPers than it is to alert them (albeit a bit stridently) to a buggy dev tool.

dratti wrote: Its obviously MS's fault If you're so confident that MS is blameless in this, I suggest you go give this ANALyzer a whirl. Make sure you select an app you've spent a considerable amount of time working on, and make sure the app name has a space in it.

And which would you suggest? The soapbox seemed a bit too obscure.

If any MS buttheads are listening, go see if you can find the incompetent asshole responsible for the 'Windows XP Application Compatibility ANALyzer. This low-grade shareware quality piece of s&%t is supposed to test an app's readiness for inclusion in the 'Windows Catalog'. A do-nothing MFC app (MFC 7.1) causes a number of errors in the Obsolete API category... but that's only a hint of the fun that's about to start. I tried running a non-trivial app with this joke of a test tool. It wouldn't run at all - but not because it failed a compatibility test (no test other than the obsolete API was selected, and the app uses none, except those included in the MFC code). Experiments indicate the reason it wouldn't run is that a folder in the path, and the app name itself, have spaces in them. The 'tool', if one was to so glorify this piece of puke, is apparently unable to deal with this test of programming skills. But wait - that's only the start. Since the failed attempt to run said app under the Compatibility ANALyzer, it now won't run at all. Apparently a registry/system modification is made by the ANALyzer such that all attempts to run said app will log ANALyzer data. But since the ANALyzer is incapable of dealing with a space in the path, it is now impossible to run said app at all - either through the VS.NET 2003 IDE, or even by double clicking the file in Windows Explorer. I removed the app entry from the ANALyzer's list, to no avail. I've uninstalled the ANALyzer and the modifications remain in place. I've searched the likely locations in the registry to try and find the offending entry, with no luck. So not only does the tool not work for s$&t, it now prevents me from (apparently) ever running that app/working on that project again, unless (it seems) I re-format my HD and re-install everything. Oh yeah, I'm going to try that again! Ask me if I f#$%*&g care about inclusion in the goddamn Windows f^^&$#g Catalog!!! At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux.