|
-
September 19th, 2010, 10:44 AM
#16
Re: How to catch error happening AFTER the code / application
 Originally Posted by LeanA
Hi all, thanks for replying
@itsmeandnobodyelse
I tried using HRESULT hr = CoInitializeEx(0, COINIT_MULTITHREADED); as well as HRESULT hr = CoInitializeEx(0, COINIT_APARTMENTTHREADED);.
Unfortunately, both failed.
@ADSOFT
I tried removing that but it errors. Just initializing the PxeAuthClass using errors.
Code:
IPxeAuthClassPtr pxecls;
hr = pxecls.CreateInstance(CLSID_PxeAuthClass);
Might you have some suggestions how to 'silence' this error so that if I run the .exe program, it will not crash?
Thank you!
It's been a while since I've done COM stuff. Maybe even if you initialize a COM object you have to delete the object before the program ends. Others that are doing COM stuff might be able to jump in.
If it were me I would do two things.
1) Look for example on how to use IPxeAuthClassPtr. I did a search, there IS some stuff out there.
2) Brush up on programing with COM objects. Once you know that you should be able to determine if the COM object is working properly. The problem with sample COM code is that they assume you know how to use COM components. There is alot of stuff out there on using COM objects (initializing, terminating, etc).
Rate this post if it helped you.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|