Why does calling SetWindowLong(Handle, GWL_USERDATA, (long)5) where Handle is a SysLink control, makes the application non-responsive and crash on an XP system? It seems the syslink control is using itself the GWL_USERDATA when it should definitely not, since it is supposed to be reserved for the application. -- The GWL_USERDATA value belongs to the window class. You are misinterpreting the word

I have not had the chance to test with other OS's yet, but I have some drivers that I think are preventing my XP Pro from shutting down (a common problem with XP). as a result, I have been forced to try alternative means to restart my computer. my next try is with InitiateShutdown(), because ExitWindowsEx failed to shutdown the machine using the example code. it would shutdown to the point

Windows Presentation Foundation SamplesThemesUpdated: February 2009The theme files in this section are created from the resource dictionaries containing each Windows Presentation Foundation (WPF) theme and are provided as examples of how to create themes, as well as how to customize existing controls. In addition, the theme files should give you some insight into creating robust controls. You can

"when you compile a program under Windows Vista, the new Vista style File Dialog will be used"This statement is wrong.It does not matter whether you compile on XP, Vista or 7.If you set bVistaStyle to FALSE, the old behaviour of XP can be forced. You can use customized open dialogs as used under previous Windows Versions.Important is that the new behaviour of Vista and 7 will be used if you compil

When I debug this method with VS2008 in XP and Vista (both 32 bit & 64 bit) , it behaves differently, can anybody tell me why?For Vista I had to write additionally System.Threading.Thread.Sleep(10000);

This exception can occur when a .NET application running on a 64-bit platform attempts to load a DLL that does not support native 64-bit execution. If the application is built in platform-agnostic (i.e. "Any CPU") mode, it will launch in 64-bit mode on the host operating system, leading to this problem. To fix this, you can force the application to run in 32-bit mode by compiling for x86 architect

This exception can occur when a .NET application running on a 64-bit platform attempts to load a DLL that does not support native 64-bit execution. If the application is built in platform-agnostic (i.e. "Any CPU") mode, it will launch in 64-bit mode on the host operating system, leading to this problem. To fix this, you can force the application to run in 32-bit mode by compiling for x86 architect

FYI,The first PGM page states that:Windows XP: PGM is only supported when Microsoft Message Queuing (MSMQ) 3.0 is installed.However, the statement in this page states that:Windows XP: Reliable Multicast Programming (PGM) is not supported.Maybe this should be corrected,ThanksVJ

I have an application (VB.Net) that uses Socket.Disconnect(True). It works correctly on Server 2003 / Windows XP machines, but when I run the application in a Server 2000 environment, I get this exception:System.PlatformNotSupportedException: Feature requires Windows XP or later.at System.Net.Sockets.Socket.Disconnect(Boolean reuseSocket)I checked this page (http://msdn.microsoft.com/en-us/library

By the way... the warning above also applies for Sleep(0).