Glad the code I shared helped. So the quickest way around this I can come up with right now is the following:

However, the problem here is: if you XML actually contains a LF (instead of CRLF) that is what you will get with the default classes. To workaround CR being in the file you can do one of the following:

• Write a NewlineCorrectingXmlReader, that takes a XmlReader in its constructor and corrects the newlines. (Probably the simplest)
• Write your own XNodeXmlReader.

Hope this helps.
Jonathan

I came across an old piece that you wrote on Serialization using XElements. Really nice little snippet that I’m using now BUT the reason for the email is to ask if you know how to address the problem of deserialisation of carriage returns. I’m no expert on this but from what I see an XmlTextReader is needed to overcome this but an XNode can only create an XmlReader which has no options for affecting whitespace. (\r\n gets deserialised to \n).

Anyway. I’d appreciate a quick response if you think of a way to solve this.

Cheers,

Jules

I replace the line: var res = (T)appDomain.CreateInstanceAndUnwrap(typeof(T));
by this line : var res = (T)appDomain.CreateInstanceAndUnwrap(typeof(T).Assembly.FullName, typeof(T).FullName);

Otherwise very useful code :)

we at InishTech (www.inishtech.com) would like to support your efforts on Monoflector and are trying to get everyone interested sit at a round table. Could you please supply me with an email adress where I can reach you to forward you some more details?

Regards,
Johannes

Wire in the PrimaryAppDomainManager via the configuration element I linked to.
First line of Main() call PrimaryAppDomainManager.Initialize();
The current domain (original startup in other words) is the primary domain because the .Net runtime wired in the domain manager for you.

I’ll follow up when I get time.