C#

public class Entity1
{
    public string SomeProperty { get; set; }
    public string Name { get; set; }
}
public class Entity2
{
    public string SomeProperty { get; set; }
    public string Name { get; set; }
}

Bastard Programmer from Hell
if you can't read my code, try converting it here[^]

Kevin Marois wrote:

so the guy who wrote them decided to duplicate the forms instead of making one form that works for both. So I'm refactoring them.

Kevin Marois wrote:

What is the right way to work with this object?

jschell wrote:

 
Obviously a good decision by that person because they are in fact
different.
 
The fact that there seem to be common components between
them is NOT sufficient reason to assume that they are the same. As an example
the fact that Word and Visual Studio both allow me to type text doesn't mean
that those two code bases should be merged.

jschell wrote:

The right way is to re-assess the decision to combine them in the first place.
Nothing you have posted here suggests that they should be combined. And in fact
what has been posted would suggest that they should NOT be combined.

Kevin Marois wrote:

This is an entirely stupid argument.

Kevin Marois wrote:

You're saying it's ok to have 2 entirely duplicate forms and their code becuase the data they work with is different

Kevin Marois wrote:

There is NO good reason to have 2 identical forms.

public interface IEntity
{
    string SomeProperty { get; set; }
}

public interface IAnotherInterface
{
    string Name { get; set; }
}

public class Entity1 : IEntity, IAnotherInterface
{
    public string SomeProperty { get; set; }
    public string Name { get; set; }
}

public partial class Form1<T> : Form
   where T : IEntity

void SetSomeProperties()
{
    (entity as IEntity).SomeProperty = "foo";
    if (entity is IAnotherInterface)
    {
        (entity as IAnotherInterface).Name = "bar";
    }
} 

this.numericUpDownAccount.ActiveControl.Refresh();

Bastard Programmer from Hell
if you can't read my code, try converting it here[^]