Question

To my surprise i’m able to do this:

public abstract class BaseComponent
{
    protected GameObject GameObject;

    internal BaseComponent(GameObject gameObject)
    {
        GameObject = gameObject;
    }
}

public abstract class BaseComponent<TComponent, TManager> : BaseComponent
where ...
{

}

1. Is naming my 2 classes the same bad practice?
2. Is there a standard naming convention in this case?

Answer 1

Is naming my 2 classes the same bad practice?

No.

Is there a standard naming convention in this case?

The same name is fine. cf. IEnumerable and IEnumerable<T>.

To my surprise i’m able to do this:

Why is it a surprise? It’s intuitive, and is standard in the framework.