> At my company, we want to use NAnt for its build > automation features, but we're also a bunch VS.Net > users. Having to create a separate NAnt project is a > bit of drag - even worse is keeping it synchronized > with the VS.Net project as it evolves. Slingshot > helps, of course, but a task that builds directly from > the VS.Net project file would be even nicer. Of > course, VBPROJ and VCPROJ tasks would likely follow.
Since I separated the core SLiNgshoT code into a separate assembly, it shouldn't be too hard to re-use the code in there that parses .sln and .csproj files. It would be even easier to have it convert the solution to a build file in some temporary directory behind the scenes and then invoke a nant task on that. Jason ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
