September 7, 2008 08:40pm pdt

1. jkr 18,350
2. DanRollins 13,250
3. fridom 13,050
4. alb66 5,750
5. kaylanreilor 5,000
6. Gurudenis 4,900
7. TheLearn... 4,000
7. LordOfPo... 4,000
9. jaime_oliv... 3,850
10. JohnGaby 3,800
11. AndyAins... 3,400
12. graye 3,000
13. vachooho 2,620
14. BlueDevilF... 2,500
15. xuserx2... 2,000
15. slam69 2,000
15. Merete 2,000
18. EDDYKT 1,500
18. meverest 1,500
18. Hardi 1,500
18. tmedley 1,500
22. GrahamSkan 1,400
23. vadimrapp1 1,000
23. evilrix 1,000
23. souseran 1,000

1. jkr 47,100
2. fridom 19,350
3. DanRollins 15,250
4. mahesh1... 6,500
5. alb66 5,750
6. TheLearn... 5,000
6. kaylanreilor 5,000
8. Gurudenis 4,900
8. AndyAins... 4,900
10. itsmeandn... 4,075
11. LordOfPo... 4,000
12. jaime_oliv... 3,850
13. JohnGaby 3,800
14. peterchen 3,600
15. graye 3,000
16. vachooho 2,620
17. alexcohn 2,500
17. jasonclarke 2,500
17. BlueDevilF... 2,500
20. alexo 2,000
20. DaveMon 2,000
20. drichards 2,000
20. harfang 2,000
20. surajguptha 2,000
20. roos01 2,000
20. KCTS 2,000
20. pjasnos 2,000
20. ivanblue 2,000
20. shout77 2,000
20. sognoct 2,000
20. slam69 2,000
20. gelbert 2,000
20. angelIII 2,000
20. AlexFM 2,000
20. xuserx2... 2,000
20. sh0e 2,000
20. Merete 2,000
20. stammencm 2,000

07.01.2008 at 07:06PM PDT, ID: 23532288

	[x] Attachment Details

How can I catch Illegal Operation errors in a third party COM object?

Asked by blowfly in Windows ATL / WTL / COM Programming, Microsoft Visual Basic.Net, .NET Framework 3.x versions

Tags: VB.NET

I want to run some code in VB.NET, which calls a third party COM object. Unfortunately, I don't entirely trust the COM object, and on our production server we want to handle it crashing to allow the rest of the program to continue.

Unfortunately, during simulated crashes, the Try/Catch/End Try routine doesn't catch Illegal Operation errors in 3rd party COM objects - it simply shuts the program down. However catching and handling these errors is essential to the reliability of our system.

Is there anything in the Threading, or Interop libraries which allows you to control, handle, whatever any IO errors in these COM objects? I vaguely remember a colleague about 7 years ago developing some IO error handling routine in C++, so I'm pretty sure it's possible.

Thanks for your time,
-blowfly

Start Free Trial

Keywords: How can I catch Illegal Operation error…

	Title
1	Illegal signage?
2	illegal start of expression
3	Using GUID As File Name
4	illegal characters and utf-8 encoding
5	Error adding library to LotusScript library
6	illegal operation

Loading Advertisement...

20080716-EE-VQP-32 / EE_QW_2_20070628

How can I catch Illegal Operation errors in a third party COM object?

Asked by blowfly in Windows ATL / WTL / COM Programming, Microsoft Visual Basic.Net, .NET Framework 3.x versions

Tags: VB.NET

About this solution