How about this. We keep the nant files for awhile and I will write an XSLT or a C# program to actually _generate_ the nant files from msbuild. In exchange, we have to actually make a decent effort at making some elegant msbuild files. None of this "PreBuild", "PostBuild" crap.. isn't there something like nant's:
<csc blah> <csc blah> <cp blah> IE, a more "command" or "script" oriented way to do it? I will also play around with MonoDevelop and see if it isnt working better for me. But if not, thats why I'll still have my wonderful nant files (I don't think I could EVER strike the command 'nant' from my mind immediately after making changes-- its ingrained). See, I'm on a different PC now with more memory-- it should be able to handle it I think. We'll see. Oh, and Happy new years everyone! On Dec 30, 2007 6:55 PM, Bruce Markham <[EMAIL PROTECTED]> wrote: > This is a very interesting and involved issue. > > I personally have not been following the Mono mailing list like I should, > (and certainly not NAnt), but I know that NAnt in its current incarnation is > wonderful for what we need. > > I like MSBuild, but it can be a bit clunkier at times. But I do know, that > technically it can do everything we are doing with NAnt. > > As far as the recursive file includes, I originally dropped those in so I > wouldn't miss something that xfury dropped in, (him being currently the > equivalent of notepad-bound, even if it does have syntax highlighting.) But > if xfury is amenable, maybe we could convince him to use MonoDevelop, if it > is indeed capable of handling the MSBuild format. And then we can toss out > the recursive includes. > > I have not worked with YAML, or CAML, or anything close. (Even the F# > samples I've seen online, both confuse, and scare the living crap out of > me.) So the potential "Yabble" example posted, literally, doesn't mean > anything to me... sorry... > > I do know, however, that any solution (no pun intended), that involves > closing and re-opening SharpOS in *any* IDE, on potententially a large > percentage of working copy updates, is not a solution. And any "solution" > that involves the IDE's build process to stub out to NAnt or another build > tool, which breaks IntelliSense, is *definitely* not acceptable. > > So for right now, I would suggest we keep doing what we've been doing, and > let MonoDevelop work out its own bugs. (And as a project, we'll "upgrade" to > the VS 2008 MSBuild format after the IDE has seeped into mainstream usage - > and still keep NAnt on the side.) I mean, I wouldn't object to MSBuild-only, > but we have to make sure everyone can play, first. And for now, using NAnt > relieves us of that problem. > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > SharpOS-Developers mailing list > SharpOS-Developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sharpos-developers > > -- fury long name: William Lahti handle :: fury freenode :: xfury blog :: http://xfurious.blogspot.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
