From: Carl Daniel [VC++ MVP] on 24 Sep 2006 10:07 DHarray wrote: > Hello, > > i have a small app with some ShellExecutes. > for example this one: > > ShellExecute(hWnd, "open", "http://www.domain.com", NULL, NULL, > SW_SHOWNORMAL); > > Everytime i debug my app and this command is executed, the debuger > will output the following: > > First-chance exception at 0x7c812a5b in explorer.exe: Microsoft C++ > exception: CError at memory location 0x00fce708.. > > i also tried ShellExecute(NULL, NULL, ...). > > What's the reason for this simple shellexecute and why is a > First-chance exception thown here? A first-chance exception that isn't followed by an unhandled exception is simply an exception that was thrown and caught inside the function you called. Various Windows API functions throw and catch exceptions internally under normal circumstance. They're nothing to be concerned about unless they're leaking out as unhandled exceptions, which would indicate that an unexpected exception occurred, in which case something is definitely amiss.' -cd |