Software

Is there some reason why you aren't using serialization?

I do this sort of thing with extension methods.

put all the calsses and their 'nornal functionality in one assembly.
Craete another assembly add a static classv for each one you want to load (same name is convenient) with a load method that extends the class to be loaded.

e.g.

internal static class SomeClass
{
public static SomeClass Load(this Some.Other.NameSpace.SomeClass argTarget, String argXmlSnippet)
{
}
}

this in loader dll would instantiate some class from someother dll, and fill it in from the xml.

Hths