Wednesday, February 21, 2007 10:41 AM
I've installed Windows SDK RTM and associate the SDK with Visual Studio 2005 by clicking "Integrate Windows SDK with Visual Studio 2005" in the start menu.
But after doing so, some of my projects cannot be built any more. After some investigation, I've found that there're several missing files. For example,
are missing. They're in the Platform SDK included in Visual Studio 2005. So can I use the 2005's include files anyway or are there any other workaround for this?
Thanks in advance,
Monday, February 26, 2007 10:52 PM
WinAble.h is no longer distributed in the Windows SDK for Vista. You should be able to use WinUser.h instead.
Oleacc.idl is also not in the Windows SDK for Vista, but oleacc.h is. Does this provide acceptable functionality?
Tuesday, February 27, 2007 12:12 AM
I understood the situation.
But the problem is that we have so many legacy codes which depends on these files and the codes should keep compatible with older Visual Studio/Platform SDK versions.
So I want to make some ifdef to identify the Windows SDK case but are there any good symol to know whether the SDK included is Windows SDK or not?
Monday, March 05, 2007 10:47 PMThe is no symbol specific to the Windows SDK, but you can use WINVER, defined in WinDef.h
Monday, November 12, 2007 9:40 PM
Can i use MSAA to build 64x application?
Thursday, April 03, 2008 4:47 PMYou have to have oleacc.idl if you are building other interfaces on top, so that you can include the oleacc.idl file.
Why was this removed?
Friday, April 11, 2008 12:36 AM
Michael, I assume you're asking about winable.h and not oleacc.idl. oleacc.idl is in the current Windows SDK and Visual Studio releases.
winable.h was moved from the Windows SDK in July 2005 because functionality was duplicated in winuser.h. It was determined at that time that efforts would be better spent on updating winuser.h to Windows Vista-level functionality rather than updating the functionality of both files.