Why do they take a commonly used function that has been well documented for over 10 years and put it into a different DLL in new versions of Windows? Is it even possible to try to include it from both DLLs using the standard way with the import section that gets populated at startup, or do we have to manually look these functions up at runtime in our programs with special-case Windows-version-dependent checks now? :/
So much for improving backwards compatibility!!



[offtopic]Why does this forum still not support parentheses in URLs? :/
I remember it having this problem over a year ago...[/offtopic]

[edit by loco]Replaced ( with %28 and ) with %29 to make PHPbb recognize the URL

What's the bother? If you're doing assembly programming, simply keep using EnumProcesses() from PSAPI. If you're doing C coding, don't define PSAPI_VERSION to "2 or greater".

As to why it was moved, it's probably because of the MinWin effort... if you want to get an idea about some of the efforts that went into Win7, I suggest you check out the two interesting Mark Russinovich videos on Channel9.

Inside Windows 7
Inside Windows 7 Redux

Ah. My mistake, sorry. I thought they were going to remove it from PSAPI.

Don't think so - and they could always make psapi forward-import from kernel32