Perhaps it might be better to design an .xsd and use the automatic XML
deserialization routines. I've found that this way is much cleaner than
the methods used in the current <solution> and <slingshot> tasks.

Using the xml de-/serialization way is fine for .csproj,

but I don't see this happening for .sln. Also, xml de/serialization

tends to set some requirements (get/set combination, ...) which are

not always desirable. But it's definitly something I'll look into.

I do plan to put an xml schema on top of the object model.

Bernard Vander Beken wrote:

Hello Yves,

Have you looked at the parsing logic and object model in Slingshot, a
tool and task included in NAntContrib?

Although it is considered 'obsolete' and does not support Framework
v1.1, it seems like a clean starting point.

Best regards,

Bernard

Thanx, I'll have a look at it.

Re: [nant-dev] Solution/Project Parser

Reply via email to