Well, a very large part of the Windows software base does work unchanged on Windows Vista (although custom actions in Windows Installer are problematic due to UAC changes [*], so installing them might be tricky). But that's the point - it's unchanged. You can run it equally well on Windows Vista or on Windows XP. The few cases where they've forced it are some of their own games (um, Halo 2 on Windows? barely uses DX10 from what I've heard). Office 2007 works on both, you get slightly more Glass in the window on Vista, big whoop. No major advantage in getting Vista over XP. It would help if Microsoft would support something other than just their latest developer tools, and that not even very well. :mad: I actually can't use Windows Vista at work because I still need to use eMbedded Visual C++ (3.0 AND 4.0) and they simply crash. No fix planned because, well, they were free, and they're out of date anyway. VS 2005 'replaces' them - if you only want to support CE 5.0 and Pocket PC 2003 and later. Sorry, I still have some customers with PPC 2002 and Windows CE 4.2 out in the field, and MFC/CE 6.0/3.0 (it's a bad hackup of MFC 6.0 for the desktop) to ATLMFC 8.0 is too big a jump anyway. [*] This is because users normally installed as administrator. If your custom action requires administrative privileges you were supposed to say that it shouldn't impersonate the installing user, but few did (and IIRC the 'no impersonate' is not set by Visual Studio for VS-generated packages). Under Windows 2000 and XP, it was possible for an administrator to mark a package for installation by unprivileged users, where you'd get bitten by this, but this feature only makes sense in managed environments and isn't used much.
DoEvents: Generating unexpected recursion since 1991