Hi Simon,
Visual C++ support in <solution> is indeed not very
good right now. Would it be possible to create diffs against current CVS and
post them to the list ?
If that's too much trouble you can just send the modified
sources.
Thanks !
Gert
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Simon
Keary
Sent: woensdag 17 november 2004 15:05
To: [EMAIL PROTECTED]
Subject: [nant-dev] How to contribute <solution> task fixes
Sent: woensdag 17 november 2004 15:05
To: [EMAIL PROTECTED]
Subject: [nant-dev] How to contribute <solution> task fixes
Hi,
Firstly, thanks for a great tool.
Whilst testing the <solution> task on an (apparently) fairly complicated .sln I found a few problems which I think I've addressed and can now get nant to build my solution. Most of the problems were dealing with settings on vc projects and reference handling.
I made the changes against a fairly recent 0.85 nightly build and am not sure what the best way to contribute these fixes as I haven't contributed to the project before. Should I send a zip of the changed files or file diffs to the list so they can be reviewed etc? Btw, I haven't used cvs for a long time but use should be able to use it if this is the best way to contribute the changes.
Thanks, Simon
------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
