Catching Errors

[Frantic]

In my most recent project I wrapped try/catch tags around almost every function and left the catch section blank. Is this good practice for catching errors?

I figure if there is going to be a bug and an error occurs it is better to proceed and not notify the user. This could impede sales.

Suggestions?

[dirkfirst]

I don't think putting a try/catch around everything is the best idea. I've always read that you should only use a try/catch if you know what to do with the error. In other words, if you don't know what will happen don't do it!

[Frantic]

So, in other words, I should just let errors crash my programs?

[TcM]

perhaps you could make an Error report system?

[Jordan]

An Error Report System is very good for capturing bugs. You may want to think about doing this.

[TcM]

Yeah any after all you will know what is happening with your software the crashes etc.. its a very good thing to do and it should be simple to do ( well I dont know in C# ) but in the languages I know its simple to make!