I have a routine that is called when an unhandled exception occures.It is called by the MyApplication_UnhandledException method in applicationEvents (which handles Me.UnhandledException)
I am looking for some code that manages disects the data provided to generate information that is of benefit to the debugging team.
I'm coming from the Winforms world where I trapped everything and handled errors with messages to the user with MessageBox.Show(ex.message) or just logged it.Now I'm in the web (MVC 3) world and I can't seem to find a definitive coded example of how to employ proper error handling. Let me show you what I'm using:
User clicks on a link which runs a controller action:
[Code]...
Then it falls to the catch block, and then routes to the HttpError action.. Twice! and then my Error.aspx view never opens, instead I get either no JSON result or a 500 internal server error... makes not a lick of sense to me. Basically, I don't know what I'm doing.
Code:
Public Function ScreenScrapeHtml(ByVal url As String) As String
Dim objRequest As WebRequest = System.Net.HttpWebRequest.Create(url)
[code]...
If it cant reach a URL it will give me this error:
Code:
Webexception was unhandeled:
Dim sr As New StreamReader(objRequest.GetResponse().GetResponseStream())
How I can add some error-handling to this code? Like if it cant reach a URL.
When two computers are connected through TCP, and one of them closes and breaks the connection, it throws error 10054 "Remote host forcibly closed the connection".I want to handle this error because I know it will happen more often than not with the application I'm building. In System.Net.Sockets.SocketException, there is an on the error code. But when I run the program, the exception that is being thrown is System.IO.IOException, and the GetType for IOException is the socket exception. I don't know how to handle the socket exception if it's not the root cause of the exception.
Here is the code for my Try Catch block:
For infiniteCounter = 1 To 2
infiniteCounter = 1
[code].....
I have a delete button in a datagridview. The button works fine however when there is nothing to delete it throws an index out of range exception. Now I know for a fact people are going to click that button even though there is nothing the I am presuming the best course of action is going to be a try/catch but I am not sure how to do it. My code is as follows,
Private Sub DataGridView1_CellContentClick(ByVal sender As System.Object, ByVal e As System.Windows.Forms.DataGridViewCellEventArgs) Handles DataGridView1.CellContentClick
If e.ColumnIndex <> 7 Then
[code].....
I'm trying to teach myself how to create multi-threaded applications in Visual Basic Express 2008. I found a page headed "Creating Threads and Passing Data at Start Time" in the Library here -
[url]
However, I can't get any of the examples on that page to run. I pasted the code from an example into a new Project in my IDE but pressing F5 just gives me build errors which I have no idea how to resolve. It's probably something trivial but I can't progress with these examples. Please can somebody tell me what I need to add to get them to run
I have an object, say Order where if an error occurs, it raises the ErrorOccurred event. If I'm running some code in say, the codebehind for a .aspx page with an public Order registered as WithEvents and I want to check to see if an error has occurred before I run more code, how do I do this? I can't simply check theOrder.ErrorOccurred. Do I have to create a local boolean flag that switches over in the event handler (OnErrorOccurred)?
Example:
Public WithEvents theOrder As New Order
Public Sub DoStuff()
theOrder.DoSomething()
If theOrder.ErrorOccurred Then
[code]....
I have some VB6 code that instantiates a class which handles events that are being raised from a VB.NET component. The VB6 is pretty straightforward:private m_eventHandler as new Collection
public sub InitSomething()
dim handler as EventHandler
set handler = new EventHandler
m_eventHandler.Add handler
m_engine.Start
[Code]...
My problem is that when I debug the VB6 program, the first time InitSomething gets called, the event will not be handled (the VB6 event handler is never entered). Subsequent calls to InitSomething does work.
Everything works as I would have expected when I run the program outside the debugger. At this point, I'm not even sure if this is something I should be worried about.It may or may not be relevant but the VB.NET was converted from a VB6 using the Visual Studio code conversion tool (and subsequently manually cleaned up).
What error handling should be used in VB.NET? Should one use the "On Error Goto ErrorHandler Exit Sub ErrHandler ... End Sub" pattern or should you use the "try {... } catch {...} finally {... }" pattern?
View 4 RepliesIn my vb.net application if I have a known set of Error Strings i.e.
Failed because I don't know about it
Failed because I know about it but I can't find it
Failed for another reason
[code].....
I am just doing a bit of error handling. I am just check to make sure that a user has selected an option within a combo box (named cbtitle1) and if option has not been selected throw an error message to tell the user.this if statement is within a save button which once a user click save this error checking runs first then if combo box has an option selected the save goes ahead else it throws an error.I can stop the save function OK but I wanted to put a error icon in with the message box but I get an error when I add it.[code]
View 3 RepliesObviously error handling is a major factor in making a good application. If a error happens letting a user know what has gone wrong.But some times error handling may(i think) not be needed. Example.
Private Sub RemoveCheckedl()
Try
For Each Item As ListViewItem In lst.CheckedItems[code]....
also when error handling it's could to think about what type of errors could be made.
Catch ex As Exception
MessageBox.Show(ex.Message, "Error", MessageBoxButtons.OK, MessageBoxIcon.Error)
even though this catches the error and displays a msg, it may not be a great message for the user so he/she can understand.
I am working on an executable to load set of data into databases.I will be running it as a windows service. I will be doing several different checks to see if the fields exists in the incoming files. When i do the checks using if statements.I would like to stop processing when a major error occurs or when any thing is interrupted Like say windows crashed. I would like to create an error file with the error message in it for that particular file. I would be monitoring error folder everyday to check if there are any errors.
View 1 RepliesWhen debugging a program, instead of doing this on EVERY piece of code:
Try
MyFunction()
Catch ex as Exception
MsgBox(ex.Message)
End Try
Is there a way to apply that to everything error I encounter without writing it on every function/sub/etc?
I am trying to create a ContextMenuStrip where I add a certain amount of ToolStripMenuItems based on how many columns are in a DataGridView via code. I am wondering, since I am creating all these ToolStripMenuItems in code, how would I handle the "CheckStateChanged" event on all of them separately? Or how can I figure out which one of those ToolStripMenuItems was clicked?
Here's a code example of what I mean:
Private Sub CreateCMS()
Dim CMS As New ContextMenuStrip
Dim TMS_Main As New ToolStripMenuItem
[Code].....
[2005] Handling Events With ToolStripMenuItems Created With Code
View 2 RepliesI am using try..catch for error handling. I am getting the message displayed as
messagebox.show (ex.tostring)
But it gives very long message.Is it possible just to get only the actual error or I could give my own modified message, based on what ex contains?
I am executing a SQL Server 2000 DTS package using C# by following the code from this article [URL]. once the package is executed I am looping through each step to find out if any step has failed and get info about error if it has failed. I also use this information to find out if the package has succeeded or not (package failed if anyone step has failed).
[Code]....
I am looking at implementing a Web Service API for our product. I have figured out how you go about the general architecture/fault handling within WCF. My question is a more general one of how to design the overall error handling system. For example I have a method called SaveCompany (companyobject). Each company name needs to be unique. Say you tried to save a second company called "ABC Inc.". Would you expect to get back a fault named "DuplicateCompanyFault", or would you expect to get back an error code, or something else? I guess the root of my question is would you prefer to receive faults to handle, error code, or some combination? These services are going to be consumed by multiple different entities outside our company on multiple non-.NET platforms.
View 2 RepliesI am creating function for search data using textbox and button. i want to put an error handling in my code which if the data was not found then it will appear in message box "Data is not found. For your info i am using visual studio and sql 2005. Here is my code and i also attach my picture
Private Sub Search_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnsearch.Click
Me.StaffBindingSource.Filter = "NAME = '" & Me.txtsearch.Text & "'"
[Code].....
I have an issue with handling errors in procedure calls in VB6.
View 6 RepliesI use a standard error handling routine in my methods that looks like the following:
Try
Cursor.Current = Cursors.WaitCursor
Cursor.Current = Cursors.Default
[code].....
I used the following code(with bug):
Code:
For n = 0 To 100
If saveLine(n).Substring(0, 8) = "heading:" Then
cboSelect.Items.Add(saveLine(n).Substring(8))
End If
Next n
The For loop only ran 5 times. It turned out that saveline(5) was shorter then 8 characters, so I changed the code which solved the problem:
Code:
For n = 0 To 100
If saveLine(n).Length > 8 Then
[code]....
VB 2010 neatly exits the for loop when the bug occurs. In this case it was easy for me to pick up the bug, because the combo box was not properly populated. What if it was not obvious that the for loop did not complete? It is quite scary to think that bugs like this are not displayed at run time.
We are developing an application for our shop floor. This program will be tracking material through the shop and we need to capture any errors the program generates, but we don't need to stop the program for all errors. I have some code to do a screen capture and put it in a database with exception.tostring data for debugging.
What we would like to do, is create an exception from the base class, but provide additional properties to allow us to set a severity and a user friendly error message. I would like to encapsulate this in a class that we would call in the catch of a try/catch, set the properties on the class, have the class record the data to the database, then raise the exception to the main program to display only the user friendly message and severity. The main program would then determine the severity and based on the severity stop the program or just display a discreet msg and continue to process.
Does anyone have an example of a custom exception class derived from exception that does something similar, or if I heading in the wrong direction, does anyone have a better solution?
Sometimes when my server is down or busy, I get an error saying "connection timeout" while connecting to MySQL. But with the error the program also crashes. My question is how can I prevent crashing, it would be better to show a msgbox when this happens. (visual basic 2010)here is a screenshot of the error
I use this,
Dim connStr As String = "Database=mydatabase;" & _
"Data Source=datasrc;" & _
[code].....
I just need a good nights sleep, but Im simply reading through a file (2010 data) and for selected teams, accessing the corresponding data for the previous year (2009 data), which is held on a separate file. (I painstakingly input all the 2009 data manually)
ds1.Clear()
cmd1.CommandText = "SELECT * FROM Teams WHERE Team = ?"
cmd1.Parameters.Add(NewSqlCeParameter("Team", (ds.Tables(0).Rows(x) ("Team"))))
cmd1.Prepare()
cmd1.ExecuteNonQuery()
[Code]...
plain how error handling scope works. What I mean by that is if I have a sub called ImportData and in there I have a for loop to go through a list of files and in the for loop I call another sub routine called CheckData. All have catch error in. If a sub has a catch error in where does it go from its call.
Private Sub ImportData
Dim iLoop as Int16
Try
[code].....
I am trying to add some error handling for AppActivate if any error occurs.I initially tried using a try statement and cancelling the sub that calls the function where my AppActivate code is, but that didn't work.I have tried looping it, changing values and everything I know. I have Googled and nothing :S
Here is my I have removed all the error handling I tried to implement, however, this commented msgbox I would like to be included (that is, possible to execute) in any methods you present.
[Code]...
I was just wondering if it is considered overkill to add:
[code]...
To every sub in your project. And what would be the side effects of this if any.
I'm kind of torn between these two error-handling models:Create a boolean Error and a string ErrorMessage property for your object. Catch all exceptions internally in the object's methods and pass the messages along using conditional logic from the caller, ie:
[Code]...
To me, it seems like the same amount of code either way, except that you have property code for the Error and ErrorMessage properties. However, you also can tell when an error occurs without having to check for exceptions. Which pattern should I go with?