Question

Possible Duplicate:
Difference between Property and Field in C#

public class Test
{
    public bool testData1;
    public string testData2;
}

or

public class Test
{
    public bool TestData1 { get; set; }
    public string TestData2 { get; set; }
}

or

public class Test
{
    private bool testData1;
    private string testData2;

    public bool TestData1 { get { return testData1; } set { testData1 = value; } }
    public string TestData2 { get { return testData2; } set { testData2 = value; } }
}

Which optimized code is better or unnecessary? And Why?

Isn’t that last one holds a lot unnecessary data?

======= EDIT:

I think in that case:

public class Test
{
    public Test(bool testData1)
    {
         this.testData1 = testData1;
    }
    private bool testData1;

    public bool TestData1 { get { return testData1; } }
    public string TestData2 { get; set; }
}

having fields in background is required. Isn’t it?

Answer 1

You should not have public fields, use properties instead so you can change the internal implementation later on if neccessary – so 2) wins. 3) is just how auto properties are implemented under the hood so is equivalent to 2)