Basically - for dynamic discovery of the types. In .NET 1.0 (when CC.NET was originally started) the types had to be hard-coded for XmlSerializer to use them, which meant that it was hard to add new tasks, triggers, etc.
We are looking at using XamlServices to handle the serialisation/deserialisation, but it will probably be a while until we swap over (it requires .NET 4.0, and since we support CC.NET on Mono we need to wait until Mono can handle XamlServices.) If you have any issues with NetReflector (and I know I have run into a few of them), post them here or on the developers' group and we'll see if we can answer them. Craig -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Cedric Sent: Tuesday, 6 April 2010 8:40 p.m. To: ccnet-user Subject: [ccnet-user] NetReflector Chaps, I was looking at the source for this project as i have a couple of ideas that i'm mulling over and i was wondering why ccnet uses NetReflector and not the built in XmlSerializer? Regards, Cedric -- To unsubscribe, reply using "remove me" as the subject.
