C#

godfetish wrote:

.I'm new to ASP.NET

public static void Main(String[] args)
{
  //Create a new Employee object
  List<Employee> mp = new List<Employee>();
  Employee e = new Employee();
  e.EmpId = 10;
  e.EmpName = "Omkumar";
  mp.Add(e);
  e = new Employee();    //<==============================
  e.EmpId = 11;
  e.EmpName = "this";
  mp.Add(e);
  e = new Employee();    //<==============================
  e.EmpId = 12;
  e.EmpName = "is a";
  mp.Add(e);
  e = new Employee();    //<==============================
  e.EmpId = 13;
  e.EmpName = "test";
  mp.Add(e);

  mp.Add(e);

Writing Employee Information<br />
Reading Employee Information<br />
Employee Id: 13<br />
Employee Name: test<br />
Employee Id: 13<br />
Employee Name: test<br />
Employee Id: 13<br />
Employee Name: test<br />
Employee Id: 13<br />
Employee Name: test<br />
Employee Id: 13<br />
Employee Name: test<br />
Press any key to continue . . .

Writing Employee Information
Reading Employee Information
Employee Id: 10
Employee Name: Omkumar
Employee Id: 11
Employee Name: this
Employee Id: 12
Employee Name: is a
Employee Id: 13
Employee Name: test
Employee Id: 13
Employee Name: test

using (WebBrowser b = new WebBrowser())
{
    b.Navigate("about:blank");
    b.Document.Title = pageTitle;
    b.Document.Write(pageContent);
    b.ShowPageSetupDialog();
    b.ShowPrintPreviewDialog();
    b.ShowPrintDialog();
}

The only programmers that are better C# programmers, are those who look like this ->

Programm3r
My Blog: ^_^

public enum StatusType {        
        New,        
        Assigned,        
        [System.Xml.Serialization.XmlEnumAttribute("In Progress")]
        InProgress,        
        Pending,        
        Resolved,
        Closed,
        Cancelled,
        None
}

public interface IValidator
{
     bool Validate(/* ... */);
}

N a v a n e e t h wrote:

Keep all the available validation classes full name in the configuration file.

N a v a n e e t h wrote:

You can use reflection to create instance of these classes. To create instance, work with Activator.CreateInstance() method. Cast the return value of Activator.CreateInstance() to IValidator and call Validate() method on this object to perform validation.

N a v a n e e t h wrote:

You can just modify the configuration file when new validator has to be added. No program recompilation is required.

neualex wrote:

If I understand this correctly, once I have all possible validation classes implemented with the same interface... should I just leave the *.cs files by themselves or do I need to compile those as well so the main class can load them?

neualex wrote:

If you happen to have a small working project similar to what we are trying to accomplish here, can you share it?

public interface IValidator
{
   bool Validate(object itemToValidate);
}

public sealed class FirstValidation : IValidator
{
    public bool Validate(object itemToValidate)
    {
        /* Your code for validation */
    }
}

public sealed class SecondValidation : IValidator
{
    public bool Validate(object itemToValidate)
    {
        /* Your code for validation */
    }
}

<applicationSettings>
    <TestApplication.Settings1>
        <setting name="ValidationClasses" serializeAs="Xml">
            <value>
                <ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                    <string>Test.First</string>
                    <string>Test.Second</string>
                </ArrayOfString>
            </value>
        </setting>
    </TestApplication.Settings1>
</applicationSettings>

foreach (string s in Settings1.Default.ValidationClasses)
{
    Type type = Type.GetType(s);
    IValidator validator = (IValidator)Activator.CreateInstance(type);
    validator.Validate();
}