add the following code: extern “C” { typedef HANDLE HCATADMIN; typedef HANDLE HCATINFO; typedef struct CATALOG_INFO_ { DWORD cbStruct; WCHAR wszCatalogFile[MAX_PATH]; } CATALOG_INFO; BOOL WINAPI IsCatalogFile( HANDLE hFile, WCHAR* pwszFileName ); BOOL WINAPI CryptCATAdminAcquireContext( HCATADMIN* phCatAdmin, const GUID* pgSubsystem, DWORD dwFlags ); BOOL WINAPI CryptCATAdminCalcHashFromFileHandle( HANDLE hFile, DWORD* pcbHash, BYTE* pbHash, DWORD dwFlags ); HCATINFO
LRESULT lResult; UINT nMsg = ::RegisterWindowMessage( _T(“WM_HTML_GETOBJECT”) ); ::SendMessageTimeout( handleToInternetExplorerWindow, nMsg, 0L, 0L, SMTO_ABORTIFHUNG, 1000, (DWORD*)&lResult); LPFNOBJECTFROMLRESULT pfObjectFromLresult = (LPFNOBJECTFROMLRESULT)::GetProcAddress( hInst, “ObjectFromLresult” ); HRESULT hr; CComPtr htmlDoc2; hr = (*pfObjectFromLresult)( lRes, IID_IHTMLDocument2, 0, (void**)&htmlDoc2); if ( SUCCEEDED(hr) ) { IHTMLFramesCollection2 *p; htmlDoc2->get_frames(&p); long lLen; p->get_length(&lLen); for (long i = 0; i < lLen; i++) {
Be careful when using _SECURE_SCL option when integrating your DLLs with DLLs you received from someone else. If you have compiled your dlls with this option but the dlls you use havent, you are most likely going to get a runtime application compatibility error. To fix this just remove this option. When secure SCL is
Below is the code to return the parent id of a process, given a process id. This can be helpful in circumstances when we have to scan all the running processes to find out the spawned processes from another process. [code language=”cpp”] // change this method signature according to your requirements BOOL GetParentPID( DWORD dwParentId,
Sometimes data is also stored as message instead of resources. the easiest way to read this is as below: ofstream myfile; myfile.open (“example.txt”); HMODULE handle = LoadLibrary(“AgentRes.dll”); // dll for reading the file DWORD err=::GetLastError(); for(int i=0;i<10000;i++) { LPTSTR lpMsgBuffer=NULL; DWORD dwRet=FormatMessage( FORMAT_MESSAGE_ALLOCATE_BUFFER | FORMAT_MESSAGE_FROM_HMODULE, handle, i, // number of the corresponding message // you
Sometimes or most times when you get a crash dump from your customer, its always good to know how to reproduce the crash and point out where the actual crash happens. Today I was debugging some bug with my lead, I found this very useful: Here are the steps: First of all open the windows
If you have a situation as above or in clear words If an application has a string localized to multiple languages and mapped to the same ID in each language, the correct version of the string might not be loaded on Windows 95 or Windows 98 using the Win32 function ::LoadString. To load the correct
I learnt this from my manager. DebugBreak is powerful tool you can use when debugging applications. I had this scenario where I need to use a java app which was internally calling C++ methods, basically JNI functions. The error in question was in the C++ side, so not really an option to use debugger. Therefore
I had an opportunity to use CListbox. The scenario was that I had to pre populate the list box and display it in a pop up window. Its very to use listbox when using it in a parent window but when you want to display it in a standalone pop up window, you would get
You would be getting this error if you tried to use CArray in VC 6. You would need to use some other way to get the values selected in listbox. In my next post I would be showing how to use two different ways to access a CListBox.
One of the simplest ways to detect a leak in your code would be to use debugCRT. Simple usage: a. Create you project in visual studio b. run the project in debug mode, then only you will find the memory leak dumps int main() { _CrtSetDbgFlag(_CRTDBG_CHECK_ALWAYS_DF | _CRTDBG_ALLOC_MEM_DF); //below call will break where the leak
This happens usually because in your visual studio vc6 compiler options you would have set the library files path to “Microsoft platform SDKs” , which uses the newer library files. Goto the option again and then set to “Microsoft SDKs” which is set to older SDK. this will help to solve your problem.
The best way is to use runas command: runas /user:test “C:Userstest_restrictedDesktopProcmon.exe”
In order to make calls to a COM method which is implemented using a single threaded model, you would need to use the CoInitialize Function. This basically Initializes the COM library on the current thread and identifies the concurrency model as single-thread apartment (STA). Format is as below: HRESULT CoInitialize( __in_opt LPVOID pvReserved ); Newer
I kept getting the above error. The most logical reason I found was related to my computer. I had installed a Antivirus called spycatcher with an out dated 4.x version. This was preventing most of my exe’s to start or run. This is just a guess. Since I uninstalled this application and everything worked fine.