I am using VB.NET 2005 to create a Windows forms application. I have a procedure named SendMail that creates an instance of Outlook.Application, to send an email from my application. I found the code on this forum, I think.The procedure works fine, but I can't use error handling with it.I call the procedure from a button click event. I put the procedure call in a try/catch block, and the application won't build, with the following error.

Error 68 'Catch' cannot catch type 'Microsoft.Office.Interop.Outlook.Exception' because it is not 'System.Exception' or a class that inherits from 'System.Exception'. C:datadevdmtiQTSQTSv7_1_20100212wQTSQTSReportsCriteriapt_frmReportViewer.vb 43 21 QTS

I'm getting 'Catch' cannot catch type 'Object' because it is not 'System.Exception' or a class that inherits from 'System.Exception'. and 'Expression detected' Code underlined in blue: Catch obj1 As Object When (?)

I have a program in VB.Net that receives mails from Outlook, extracts attachments and inserts the attachments into a table through a query. I would like to put the query/queries in a Try/Catch block, but cannot do so as Outlook exceptions cannot be caught, and it gives me an error, and unless I put a very specific exception, I cannot catch it. Is there a workaround?

Edit:

TryCatch ex As ExceptionEnd Try

Exception is underlined and when I hover on it, it says: "Catch cannot catch type 'Microsoft.Office.Interop.Outlook.Exception' because it is not in 'System.Exception' or a class that inherits from 'System.Exception'". This is affecting all my other code which I'd like to put into a Try/Catch block.

I have this scenario: in a Sub I have a Try...Catch statement.Within that Try..Catch I call another sub.In that 2nd sub is also a Try...Catch.(see below for example).Now if an exception occurs in the 2nd sub's Try...Catch, which Catch gets excecuted? The 2nd one, the 1st one or both?

It is possible to catch an exception and throw a new exception which wraps the first exception as an inner exception: [URL] Also, if I call a function and it throws a certain error, but I catch it, will the calling code's catch handler execute? If so, and it is of a higher exception type, is this not wrapping the exception? eg I can throw exception ex of type IndexOutOfRange, log it but rethrow, catch a higher up exception and do something, or I can throw a new exception and wrap an inner exception like:

The reason for doing this is that while I catch my exception on a higher level logic (to make sure I can log it properly), I need to do some actions in the event of the exception that I can only do inside my class/function.

How can I catch an inner exception in .NET? I need to check 2 databases for a record. The database code throws an exception if a record is not found, so then I want to check the second database[code]...

I've written a DLL that contains a bunch of classes. One of my methods validates the contents of a file and throws any necessary exceptions based on invalid content - I'm using a standard "throw new exception." call the thing is, when my code reaches the line where the exception is thrown, my Visual Studio IDE hangs up on that line instead of the external call to my validate method.

[Code]...

So my IDE is actually pulling up the VB file that contains the DLL content and highlights the line in the ValidateFile instead of just hanging on the oFC.ValidateFile method line where the exception is thrown instead of the IDE hanging on the oFC.ValidateFile line in my calling application.

I just want user to have access to the any exceptions that are raised. Here if "C:FileThatDoesntExist.txt" file does not exist then Dll throw exception which should be catch through Application.ThreadException.. How to Catch exception from DLL ?

System.Data.OleDbException (0x80004005): The changes you requested to the table were not successful because they would create duplicate values in the index, primary key..."I know how to catch all exceptions. But I want to catch THIS SPECIFIC ONE so I can call one of my subroutines to generate a different ID that will not violate the primary key.

I configured HealthMonitoring in my web application to log all exceptions in the database.But, when I gracefully handle some exception by showing a nice message to the user, they are not logged in the database.If I something like Throw ex, the standard error page is be displayed and the error is not gracefully handled.

Is there something else I could add at the end of my error handler to tell the system to also log this error?here an code sample:Dim errorText As String = "Doing Something"Try 'Do Something

I have one global generic exception handler(catch ex as Exception) for all unhandled exceptions from application.But in debug mode(app runs from VS) I don`t want that exceptions go to this global handler.Better for me is when VS stops app on place when exception occurs.

What is the code that I can use to describe what happens when there is not just one exception in a'Try...Catch..Finally...End Try' statement? For example: 'Catch' is used to describe what happens when a certain exception occurs, but what can I use to describe what happens when a certain exception does NOT occur?

I ran into an interesting dilemna today. I have a function that handles information and checks for duplicate values, then returns the next number that is not a duplicate. So, I have something like this:

Public Function GetNextNonDuplicateNumber(NumberToCheck as Long) as Long//the non-duplicate the function will returnDim NonDuplicate as Long'duplicateIf CheckForDuplicate(NumberToCheck) = True ThenThrow New DuplicateException()[Code] .....

As you can see, I want to handle the exception specifically, but I also want to throw it when I'm done because I want to alert other code outside the function. The problem is that simply throwing it exits out of the function with a null value.

The problem I face is when I try to get an instance to a file that doesn't exist in the VSSDB, thus leading to a COMException, which basically wouldn't be of a problem (I would expect). In fact the exception occurs, but instead of proceeding with the catch code, the debug cursor stays on the line "oItem = m_oSourceSafe.VSSItem(sItem)", showing a dialog with title "COMException crossed a native/managed boundary.

From here the execution doesn't proceed, until I change the content of sItem to an existing file.

How can I catch an exception thrown by a control event?I have a control that throws an exception in one of its events and I need to catch it but I don't know how.Consider for example that the text box control throws an exception in its click event. How can I catch such exception?

I want to catch the exceptions thrown by the login() function in JIRA's SOAP API. The function login throws 2 exceptions. RemoteAuthenticationException if the user provided an invalid username or password and RemoteException if there was some problem preventing the operation from working. Currently I'm using this code to catch the exception

A developer has created a custom control in ASP.NET using VB.NET. The custom control uses a repeater. In certain scenarios, the rpt_ItemDataBound event is encountering a data error. My goal is rather than having the user see the yellow screen of death, give the user a friendlier error explaining exactly what the data error is. I figured I would be able to use a Try/Catch block as shown below throw the exception, however, it appears that the event has nowhere to be thrown to and stops executing at the "End Try" line.

In VB.NET, I can find where the repeater's DataSource is being set, however, I can not find a DataBind event. How I can capture the exception in this ASCX control so I can report it to the user. The stack trace looks like this. There is another repeater within the repeater that is actually causing the error (rptOther) and I'm able to catch the error, but I can only throw it to the rpt_ItemDataBound. How rpt_ItemDataBound is getting called without a DataBind event.

I have inherited an old VB.net-project. The code mostly uses try-catch for error-handling. However in some places I have found If Err.Number <> 0 Then.If an error occurs, what decides if an Exception should be thrown, or just setting Err?I don't want to handle error both ways...

In my code I am trying to come up with the following messages using a try/catch Unhandled exception has occurred in your application. If you click continue, the application will ignore this error adn attemp to continue. If you click Quit, the application will close immediately.conversion from string """" to type 'integer' is not valid Warning Icon followed by 3 buttons one that saids the DETAILS, another for CONTINUE, and one for QUIT.Here is part of my code. I did use Try/catch correctly, but it doesnt say the message the way i described it above ..

This is part of my block which handles incoming messages via TCP. Sometimes it sends scrambled messages which are unpredictable and i need a Try + Catch block for it:'

[Code]...

I can either get "Input string not in correct format" or "typecast not valid". But this is simply supposed to be routine to run into and be able to handle. but that stupid error message keeps popping up I've heard of JITDebugging, should I use that?

I have a problem that adding a new ROW with duplicate UNIQUE id throws CONSTRAINTException that I cannot always catch.. Randomly general exception halts my VB software, sometimes catching works. here is my code.

In the following code an error arises because the date being passed to the cDate function is Null. However, the catch statement is in error and reports index out of range on the Catch Ex as Exception line. The exception helper says the word Exception is in error and advises that it is index out of range.

I have a system which have already handled exceptions by try-catch blocks everywhere.How do I quickly and generically implement exception logging like overriding something instead of inserting logging functions in every single catch block?