Ian MacLean wrote: > 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
This is a good idea. That might make things more manageable, too. What I usually do now to keep the generated NAnt .build file separate from my custom tasks (so that I could keep regenerating it as I make changes to the VS.NET project files) is to generate a .build file that gets <include>ed into a driver .build file that I write by hand. > >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. Yeah, it doesn't seem like a "natural" way to write a NAnt .build file but I was trying to get to a point where I could match VS.NET's ouput and that's probably not something you would typically do by hand, either. > >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. I'll try to take a look at what SLiNgshoT outputs (I've long since forgotten) to start generating some discussion on this. Maybe we could even make a VS.NET Custom Tool (like Chris Sells' CollectionGen) that can generate the .build file. The latest version of SLiNgshoT is broken up into a DLL containing the core functionality and a simple EXE driver so that it can be easily embedded by other applications. I'll hopefully get a chance to upload it tomorrow. > btw > nice article on oreillynet Jason :) Thanks. :-) _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
