very good tutorials you have here! They taught me a lot.

Just a little optimization i would like to point out (contributing back and so forth )

in GameScreen.cs

public virtual void Update()
{
// Create a temporary list so we don’t crash if
// a component is added to the collection while
// updating
List updating = new List();

// Populate the temporary list
foreach (Component c in Components)
updating.Add(c);

// Update all components that have been initialized
foreach (Component Component in updating)
if (Component.Initialized)
Component.Update();
}

Could be changed to do this:

public virtual void Update()
{
// Create a temporary list so we don’t crash if
// a component is added to the collection while
// updating
List updating = Components.ToList();

// Update all components that have been initialized
foreach (Component Component in updating)
if (Component.Initialized)
Component.Update();
}

Not sure if it would actually faster(should hopefully be), but in terms of simplicity, its a win!

Thanks again!
fused

Especially the idea of keeping the GraphicsDevice in a static field. Is there a particular reason for your decision?

I’m just interested in hearing your motivation

I started out with some static classes, but ultimately went the other way. Mainly because I wanted to use an inversion of control container and because, well, a class which takes a graphics device in its constructor is more easily isolated from the other classes than one depending a static class named X in namespace Y with property Z to exist somewhere in order to compile.

On the other hand, an all-static design might be easier to understand for people new to the topic, so maybe that’s the motivation?