C#

try<br />
{<br />
    //Your code that might generate an error goes here<br />
}<br />
catch (ArgumentException e)<br />
{<br />
    // Let's assume your method knows how to handle this exception<br />
}<br />
catch (Exception e)<br />
{<br />
    // Oops, we're out of options.<br />
    // Make the calling method handle this<br />
    throw e;<br />
}

Nico van der Plas wrote:

p.s.
Which of the Code Project gurus around here can tell me how to make the tabs in my example code visible. It looks horribly unindented now...

Mark06 wrote:

Imagine Im developing a function. I can either account for errors by using a try...catch statment, or I can raise an exception.

Mark06 wrote:

If I development a function that requires a integer parameter to be less than 10, why would I need to create an exception if its greater?

Mark06 wrote:

So therefore, raising exceptions is bad?

Mark06 wrote:

I can either account for errors by using a try...catch statment, or I can raise an exception.

Mark06 wrote:

If I development a function that requires a integer parameter to be less than 10, why would I need to create an exception if its greater? Surely Im going to be aware of that myself? Likewise, I would much rather the application deal with the problem using a try...catch, than throw an exception causing it to creash.

Mark Anthony Sabado wrote:

how to create a string array property

private string[] _myarray;
public string[] MyStringArray
{
    get { return _myarray; }
    set { _myarray = value; }
}

Regards

private System.Collections.Specialized.StringCollection _mystringcollection = new System.Collections.Specialized.StringCollection;

public System.Collections.Specialized.StringCollection MyStringCollection
{
    get
    {
        return _mystringcollection;
    }
    set
    {
        _mystringcollection = value;
    }
}