It's even worth maintaining NAnt and proj files - developers use csproj/vbproj files in VS, and building is done using 'clean' targets with wild-cards. It increases the developers overhead slightly, but the very fact that he/she must verify that files are being added to the build is an advantage in my eyes.
Perhaps we are looking at this the wrong way... Maybe there should be a plugin which will allow loading of nant files in VS.NET?
On 7/18/06,
Adam Gritt <[EMAIL PROTECTED]> wrote:
I'm not talking about spawning devenv, but moving the functionality of
the <solution> task to a separate exe that would be runnable from NAnt
and essentially turning <solution> into a wrapper around the exe.
I really don't see any significant advantage of creating a build file:
<project>
<solution solutionfile="a.sln " />
</project>
then "nanting" this instead of running a single exe file with parameters:
BuildSolution.exe a.sln
Separating the solution building algorithms outside of NAnt core (and
perhaps making it a separate OSS project) would help NAnt focus on its
core features. In a year or two there will be less and less projects
which will continue to use VS2002/2003. Having such a complicated piece
of code (and I'm sure <solution> is one) in NAnt's core can negatively
impact NAnt's future maintainability.
My 0.02
JarekWell, first the assembly that is used for the .NET builds is actually a separate assembly so it is not a big deal if the code remains there. Plus the code does support compiling for 2005 as well. One of the big features I found is that I can layout the build script as such:
<solution>
<projects>
<include name="file1.csproj"/>
<include name="file2.csproj"/>
<include name="file3.csproj"/>
<include name=" file4.csproj"/>
....
</projects>
</solution>
And nant will make sure they get build in the proper build order and alert me to if there is any circular references so I can go smack the developers. The devenv doesn't do that unless I setup the 200+ projects all in one solution which would be a real pain and take forever to load and build. I don't even have to change anything in the project files, Nant knows how to handle them so it just take and runs with them without further information on my part except for the web projects. This helps because then the developers can use Devenv to develop and I can use their files to do the build without converting them. But to add a separate exe to just do the builds would be redundant in this case because I am building it on a list of projects not a list of solutions.
Also my 0.02.
Adam Gritt
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
--
Shmarya
-----------------------------------------------------------
[EMAIL PROTECTED] - http://shmarya.net
NUnit rocks! http://nunit.com
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
