.NET Framework Bookmark and Share   
 index > 64-Bit .NET Framework Development > MSDN 64-bit issue
 

MSDN 64-bit issue

I am developing 64-bit Windows program and need to use CListCtrl and CTreeCtrl.
But there are following sentences in MSDN:
CListCtrl::SetItemData
http://msdn2.microsoft.com/en-us/library/936147y4.aspx
BOOL SetItemData(
int nItem,
DWORD_PTR dwData
);
Sets the 32-bit application-specific value associated with the item
specified by nItem.

Similar sentences appear in CListCtrl::GetItemData(),
CListCtrl::InsertItem() and CTreeList::SetItemData(), etc.

How do I understand "32-bit"? Does it mean I cannot pass 64-bit value to it?
or just Microsoft forgot to update these pages?

Where should I get help on this issue?

JessieLiu

Jessie:

Your assumption of overlooked documents is correct. The DWORD_PTR type's size depends on the platform (4 bytes on 32bit and 8 bytes on 64bit).

You can use SetItemData on 64bit and 32bit without an issue.

Jeff

Jeff Schwartz msft

Jessie:

Your assumption of overlooked documents is correct. The DWORD_PTR type's size depends on the platform (4 bytes on 32bit and 8 bytes on 64bit).

You can use SetItemData on 64bit and 32bit without an issue.

Jeff

Jeff Schwartz msft
It's 2009 and the following MSDN page still says 32 bits on all architectures:
http://msdn.microsoft.com/en-us/library/936147y4(VS.100).aspx

Will MSDN be corrected some year? Some programmers wish we didn't have to depend on undocumented behaviour.
Norman Diamond

You can use google to search for other answers

Custom Search

More Threads

• Oracle.DataAccess causes 64 bit / 32 bit error in ASP.NET / Visual Studio 2005
• why the API(SHFileOperation) will not work on Vista-64bit?
• How do I build a 64 bit exe in VS 2005
• Compiled Regexs on 64bit are very slow
• error try project only build - 2005 beta , build type x64
• How to find Kernel Memory from VB.Net
• .net app can't call COM server through interop on vista x64-works on 32 bit version
• int on a 64-Bit machine
• .NET 3.0 dependency
• .NET 'Any CPU' targeted Winform EXE runs as 32-bit on *some* Vista x64 computers