Committed first cut. Check it out and let me know what you like/not like about it.
On Mon, Jan 4, 2010 at 11:20 AM, Roelof Blom <[email protected]> wrote: > Sorry for the late reaction, I was being held up by other things. > > I will start (some time this week) with the ARIntegration facility, as you > suggested. It's nice and small and has enough dependencies as too not make > it trivial. > > -- Roelof. > > > On Mon, Dec 28, 2009 at 12:43 AM, John Simons > <[email protected]>wrote: > >> Inline >> >> On Dec 28, 3:15 am, Roelof Blom <[email protected]> wrote: >> > On Sun, Dec 27, 2009 at 3:01 PM, Markus Zywitza < >> [email protected]>wrote: >> > >> > > Looking at all those problems presented with MSBuild here, I'm asking >> > > myself why we should make this extra work. In this discussion I read >> > > about the following problems with the current solution: >> > >> > Up untill now everybody seems to present only problems with MSBuild. >> Perhaps >> > because it doesn't have very good rep, or perhaps it's because we're too >> > locked in to look at what it has to offer, especially where it's headed >> in >> > v4. >> > >> > Please read 'What's New in MSBuild 4.0' athttp:// >> msdn.microsoft.com/en-us/library/ee240939(VS.100).aspx, especially >> > the ability to create inline tasks and multi-targeting are very welcome. >> > >> > >> The new stuff for v4 sounds good :) >> >> > >> > > -You can't open a solution and hit F5 to build it. Instead you have to >> > > click "ClickToBuild.bat". >> > >> > > The ClickToBuild.bat shows that we have a build system that works. If >> > > I get a source without any build files or "howtobuild.txt", just a >> > > simple sln, I'm getting suspicious whether this is really a competent >> > > developer's project. Its simply not professional as it places the >> > > friction on the users' side of the equation. For an example, look at >> > > the Lucene.Net build instructions here: >> > >> > >https://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net. >> .. >> > >> > ClickToBuild.cmd can very easily kick off MSBuild. >> > >> I actually disagree, if I see a project with "howtobuild.txt" and >> ClickToBuild.cmd I see a complex build system that forces me to build >> their way, not the way I want. >> >> > >> > >> > > -You can't build in VS before you run a NAnt script. >> > >> > > We could add empty AssemblyInfo.cs files and replace them by NAnt when >> > > building. We would have to handle ignoring those changes in >> > > committing, though. Perhaps NAnt can make a backup copy before and >> > > restore the original file after the build >> > >> > Sounds complicated. >> > >> I've said this before and I stress it again, you can build without >> running NAnt first. To fix problems like this just do not check in >> AssemblyInfos, and voila the project now builds fine in VS. Have a >> look at Core, DP2, Windsor, EmailSender, TemplateEngine, .... >> >> > >> > >> > > -Both the .build and .csproj files need to be maintained. >> > >> > > That's right, but it only requires work when adding references to a >> > > project, not when only files are added, updated or removed. If it is a >> > > problem, we could considers compiling using MSBuild with .csproj files >> > > and doing the other work in NAnt >> > >> > This is what we use at work, and I dislike it more and more. Personally >> I >> > find using two different build tools a bit cumbersome. >> > >> Not if we complete get rid of Nant, then we only have one file to >> maintain (csproj ) and that is done through VS anyway. >> >> > >> > >> > > On the plus side of NAnt, there is the following: >> > > -Loading projects in VS isn't delayed. >> > >> > ? >> Why would I load a project in either VS or Nant if all I want is to >> compile? For that I go to the build server and get the binaries from >> there. And if I'm working on the project 9 out of 10 I already have VS >> opened so it is a lot simpler to just press F5. >> >> > >> > > -Works on both NET and MONO on Windows and Linux. >> > >> > True. But that's why xbuild was created by the Mono project. >> >> > >> > > -Has an XML schema that supports editing with VS. I still can't >> > > understand why MS created an unschemaable XML language for MSBuild. >> > >> > FWIW, you'll get full schema support for MSBuild and NAnt with >> ReSharper. >> >> csproj + sln files are also maintained via VS without any extra tools >> or xsds. >> >> > >> > > All in all, for me it is -1 for retiring NAnt. >> > >> > -1 is not really helping things, is it? And this thread wasn't even >> [meant >> > as a] a vote. >> > >> > I would like to give at least a try, before we start shooting -1's at >> it. >> >> Ok, so start with a small project, how about ActiveRecordIntegration >> facility, at the moment doesn't have anyone as the leader. >> >> > >> > Cheers, >> > Roelof. >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Castle Project Development List" group. >> To post to this group, send email to >> [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<castle-project-devel%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/castle-project-devel?hl=en. >> >> >> > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
