Jason Diamond wrote: > >of functionality) but assuming that the NAnt output was fixed, it shouldn't >be too hard to add support to SLiNgshoT to the round trip from .sln to >.build and back to .sln again if you wanted to. > that would be pretty cool. Maybe you would need to have a seperate nant file for each matching .csproj and roundtrip these only so that there are no issues with tryng to convert tasks that have no correspondence in VS.NET
> >But this assumes that you >even like the .build files that SLiNgshoT outputs and would want to maintain >them by hand. I'd love to get feedback on how it can be improved if anybody >had any. > I've been using slingshot generated build files with a few tweaks. Somthing was bugging me about the way the Debug/Release targets are setup but I haven't thought of anything better yet. > >Speaking of which, maybe a "canonical" .build file structure might be a good >idea for NAnt in general. Like I said above, there's an infinite number of >.build files that can result in the same compiled assemblies but it might be >nice to have a well defined example that people could copy or tools could >generate. I'm talking about just reproducing the exact functionality that >you get when you build your assemblies using a .sln file in VS.NET. It would >be awesome if you could build in VS.NET and then drop to the command line >and invoke NAnt and see nothing happen since everything would be up to date. >And vice versa if you built using NAnt first. Do you think we could come up >with such a beast? > I really like the sound of this. I'm in the "develop in VS.NET, build in NAnt" camp and its easy to add somthing to the csproj and forget about the .build. Maybe a cannonical .build structure for NAnt files that build C# assemblies. Ian btw nice article on oreillynet Jason :) _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
