The wise way to define a string class

Well, as it's not a public class, it's OK if you're just writing code on your own.

However, although it's more verbose, you'd be much more likely to see something like this in professionally written C# code which avoids public fields, preferring to always use properties instead. It also gives the user the option of setting the property values in an overloaded constructor:

class Item  

{  

   public string Id { get; set; }   

   public string Name { get; set; }  

   public string Title { get; set; }  

   public string Value { get; set; }  

   public string Type { get; set; }  

   public string Tagname { get; set; }

   public Item()

   {

      // either leave as null or set to empty strings

      Id = "";

      Name = "";

      Title = "";

      Value = "";

      Type = "";

      Tagname = "";

   }

   public Item(string id, string name, string title, string value, string type, string tagname)

   {

      Id = id;

      Name = name;

      Title = title;

      Value = value;

      Type = type;

      Tagname = tagname;

   }  

}