You should have a custom header. eg Content-Length: HttpSendRequest will not generate the content-length for you.

Localization / Internationization is not a simple task. It will be more complex if your application is not UNICODE app & need to support asian languages (eg. Traditional/Simplified Chinese / Japanese / Korea). Use SetThreadLocale() is fine if it solves your problem. But in my experience, it didn't. MS Press has a good book for that but I cannot find the name. There is a new book "Internationalization and Localization Using Microsoft .Net" which I havn't read.

Memory Leakage is caused by

khrstopher wrote:

delete frame;

you should use delete []frame; :omg:

You have to import the typelib of the testcom.dll into your project.

I think your application didn't have proper sync. on the thread. The problem may not be hitted in single CPU machine. It seemed to be a deadlock on the threads.

I have tried a product called 'Visual Watch' which provides such functionalities. But it doesn't support VS 2005 yet.

You havn't described "How it doesn't work". I has used it and everything is expected.

If you search "internal access modifier" in VS, you can find : <--- internal : Access is limited to the current assembly. private : Access is limited to the containing type. -->

If you search the "UnregisterClass" in VS, you can find the following in the Remark. <--- Before calling this function, an application must destroy all windows created with the specified class. All window classes that an application registers are unregistered when it terminates. --> If you have tried to unregister the class within the WM_DESTROY msg handler of the window instance, it should be failed.

In your application, (if it is a MFC application, add the following in the InitInstance()) _CrtSetBreakAlloc(715); it will break when it tries to allocation the leakage memory and you can find the source code. Details can be "Memory Leak Detection" in VS.

In Win32, sizeof(int) is 4 bytes.