XML and the Content Pipeline

re: XML and the Content Pipeline

Zyxil — Mon, 02 Jun 2008 21:21:03 GMT

So if you imported a POX (plain ol' XML) file through the pipeline, what is the runtime equivalent? Do you still have to create your own processor? If you are loading level data, for example, you would need a LevelData processor to create a LevelData object from your XML file?

What does this give me over using XMLSerializer?

re: XML and the Content Pipeline

ShawnHargreaves — Mon, 02 Jun 2008 21:30:44 GMT

> So if you imported a POX (plain ol' XML) file through the pipeline, what is the runtime equivalent?

That depends entirely on what type you are importing. There is nothing special about the fact that the data came from an XML file: after the importer finishes, it's just data. Some data has the same type at runtime as it does at design time, while other data changes type (eg. TextureContent -> Texture).

> Do you still have to create your own processor?

That depends on whether you want to process the data or not. If it's already in the exact right format, you don't need to process it. If you want to change it in some way, you do.

re: XML and the Content Pipeline

Shrdlu — Thu, 05 Jun 2008 03:24:43 GMT

Xml also comes in to play if you are messing with the content project's msbuild script or automatically generating one via code.