Automatic XNB serialization and *Content classes

re: Automatic XNB serialization and *Content classes

Kevin Gadd — Fri, 03 Jul 2009 07:26:16 GMT

Thank you for posting about this! Figuring out this problem was driving me crazy until you shared the solution on the forums. Hopefully this blog post will save other people some stress.

re: Automatic XNB serialization and *Content classes

Nez — Fri, 03 Jul 2009 16:06:18 GMT

Thats a really great solution. My only worry (which isnt exactly huge) is that you still cant constrain T - Texture2D and Texture2DContent are completely different classes, so you still rely on someone getting it right at both ends (which you do with all content loading).

But its definitely a better solution. I guess its just my pedantic nature to try to stop silly people doing things like Sprite<Audio> or some such nonsense :)

re: Automatic XNB serialization and *Content classes

Roonda — Tue, 07 Jul 2009 09:15:32 GMT

I tend to use (yet) another option which looks a bit like this:

public class Sprite

{

public Rectangle Rectangle;

public string TextureName;

public Texture2D Texture;

public void Init(ContentManager content)

{

Texture = content.Load<Texture2D>(TextureName);

}

That extra string variable does annoy me though. I think I'll experiment with the generic solution. Thanks for the post Shawn.

re: Automatic XNB serialization and *Content classes

john — Tue, 21 Jul 2009 23:04:27 GMT

Lol Shawn, well written and great content. Thankyou.