public class AffiliateConstants
    {
        private string m_AffiliateName;
        public string AffiliateName
        {
            get { return m_AffiliateName; }
        }
    }
 

In my was taught it at Uni but didn't really pay attention and havn't used it since way:

Are you looking at subclasses to pull some properties from the parent class then set the additional properties based on the subclass?

Although I have no idea how to code that.

Well basically it's just a class that loads some settings from an XML file. Included in these settings are filters and output settings. So I thought it'd be useful to have nested classes for Settings.Filters and Settings.Output- just for ease of use, really.

Going for it's own assembly seems a little excessive... I might just go down the route of making separate classes for Filters and Output and then having them as public objects inside Settings- and define their values in the constructors.

Cheers!

    public class AffiliateConstants : AffiliateConstants.IFilters
    {
        public IFilters Filters
        {
            get { return (IFilters)this; }
        }
 
        public interface IFilters
        {
            string FileFilter { get; }
        }
 
        #region IFilters Members
 
        private string m_FileFilter;
 
        string IFilters.FileFilter
        {
            get { return m_FileFilter; }
        }
 
        #endregion
    }
 

AffiliateConstants ac = new AffiliateConstants();
Console.WriteLine(ac.Filters.FileFilter);
 

private string m_AffiliateName;

if (target.GetType() == typeof(System.DateTime))
{
      target = DateTime.Parse(nav.Value);
} else {
      target = nav.Value;
}

public class AffiliateFilters
        {
            AffiliateConstants _parent;
            public AffiliateFilters(AffiliateConstants parent)
            {
                _parent = parent;
            }
            public DateTime StartDate { get { return _parent.m_FilterStartDate; } }
            public DateTime EndDate { get { return _parent.m_FilterEndDate; } }
            public String MetroCode { get { return _parent.m_FilterMetroCode; } }
            public String ZipCode { get { return _parent.m_FilterZipCode; } }
        }
 

No, that'd be fine too.

Are you using some ancient version of C#? Maybe the compiler wasn't as clever before 3.0 or something.

I'm on Visual Studio 2008 but it's targetting 2.0, so that's possibly the case.

At least I'm not using 1.1 any more. Slow progress.