xBuild and MSBuild are part of the platform sdk so when compiled in .net2.0 you can use the msbuild namespace.  When compiled against the Mono platform you can use the xBuild tasks.

The difference between xBuild and MSBuild is only the platform, they both use the same file layout en structure.  What I don't know is what happens when people create custom tasks in msbuild.  Because the MSBuild file is also the project file would VS2005 leave them, move them, modify them?  What happens when you want to run in in Mono?

What should Nant do.  Have one Build task that checks the platform and loads a platform specific assembly?  Or have different builds and in each build depending of the target there should be different class compiled?

Somthing to think about
Cheers
Dries


Martin Aliger <[EMAIL PROTECTED]> wrote:
[resent to list]

I don't know anything about xBuild, but NAnt/MSBuild/(xBuild?) etc are
mostly the same (competetive) products, varying in features, syntax,
matureness. I'm not sure whether mono team plan to mimics msbuild syntax or
not. Maybe they just developing another NAnt? Looks like time to look for
some info :-)

Anyway, it should be pretty easy to make another simmilar
to .


Regarding to task (which is mostly wrapper around msbuild.exe) -
it should be easy to redirect to xbuild.exe via nant.exe.config's target
platform exe names. (like csc->mcs redirect)

Martin Aliger


> -----Original Message-----
> From: Steve Wagner [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 14, 2006 3:52 PM
> To: Martin Aliger
> Subject: Re: [nant-dev] Release 0.85 and beyond
>
> Hi,
>
> i think, using msbuild isnt the problem on Windows machines,
> but what is with Mono? MsBuild isnt present on Unix or MacOS.
>
> But there is a 4 solution. The Monoproject writes an owen
> version of MsBuild called xBuild. Why dont cooperate with
> them an use the object model of xBuild to write an
> task.
> XBuild isnt perfect a the moment, it could compile some
> simple project, but why do the work two times.
>
> Steve Wagner
>
>
> > Hello,
> >
> > agreed - 1.0 soon is a good thing. I see only one big thing
> which we
> > should addess in 1.0: VS2005 projects. Or MSBuild
> cooperation. The same thing.
> >
> > Since many developers are migrating (or already using)
> framework 2.0
> > in
> > VS2005 and we (currently) do not provide direct tools for
> projects it
> > uses, they could either: use plain msbuild (deserters!) or use core
> > tasks-csc,regasm etc (and maintain both .csproj and .build) or (as
> > most of them do today) msbuild.exe to their .csproj
> file (and
> > give up project dependancy resolution and other features)
> >
> > As I see it, we could:
> > 1/ state, that new project files used on VS2005 are unsupported 2/
> > write new task which handles it somehow (aka or
> > )
> > 3/ merge required code into current task
> >
> > Since msbuild code need to run under 2.0 framework, and NAnt itself
> > should run on 1.0/1.1 as well, integration (if 3 will be
> chosen) have
> > to be done carefully. Or could we restrict NAnt to 2.0
> framework? I don't thing so...
> > Maybe 2 distributions: 1.0 compatible, and 2.0, compiled
> for 2.0 and
> > with additional features?
> >
> >
> > Martin Aliger
> >
> >
> >> -----Original Message-----
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED] On
> Behalf Of
> >> Gary Feldman
> >> Sent: Friday, July 14, 2006 2:47 AM
> >> To: nant-developers@lists.sourceforge.net
> >> Subject: [nant-dev] Release 0.85 and beyond
> >>
> >> It's now been almost 6 weeks since rc4 came out.
> >>
> >> There are three open bugs filed since then, none of which are
> >> showstoppers in my opinion. There are two others closed and one
> >> deleted.
> >>
> >> There are a couple of problems reporting in the mailing list since
> >> then, some of which seem significant to me. However,
> basing release
> >> decisions on items discussed in the mailing lists and not entered
> >> into the tracker is a road to chaos.
> >> It's a hard line, but somebody has got to draw it :-)
> >>
> >> My conclusion is that rc4 should be retagged as 0.85 final and
> >> announced as such. After that, I think two things need to be
> >> discussed:
> >>
> >> 1. What will constitute 1.0, and what is the roadmap
> to get to it?
> >> 2. Is a bug fix build needed before then?
> >>
> >> Personally, I think NAnt is in good enough shape to
> timebox requests
> >> for features and mandatory fixes in 1.0. In other words, set a
> >> deadline of Aug 15 (for example - I don't mean to be
> declaring dates
> >> unilaterally) for requests to come in.
> >> Two weeks later, have a final set of bugs and features
> targeted for
> >> 1.0, and a target date for rc1. Obviously show stoppers
> found after
> >> the first date can be added to the list; that date just raises the
> >> bar for consideration. Ideally, I'd like to see 1.0 final
> by the end
> >> of the year, better yet by October.
> >>
> >> My perspective on this is that releases and release numbers are
> >> largely a marketing decision, not engineering. In this
> case, I think
> >> it's important to maintain momentum and credibility
> against msbuild.
> >> Otherwise, the community of users won't grow, and hence
> the community
> >> of contributors won't grow.
> >>
> >> Gary
> >>
> >>
> >>
> >>
> >>
> >> --------------------------------------------------------------
> >> -----------
> >> Using Tomcat but need to do more? Need to support web services,
> >> security?
> >> Get stuff done quickly with pre-integrated technology to make your
> >> job easier Download IBM WebSphere Application Server
> >> v.1.0.1 based on Apache Geronimo
> >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&
> >> dat=121642
> >> _______________________________________________
> >> nant-developers mailing list
> >> nant-developers@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/nant-developers
> >>
> >
> >
> >
> >
> ----------------------------------------------------------------------
> > --- Using Tomcat but need to do more? Need to support web services,
> > security?
> > Get stuff done quickly with pre-integrated technology to
> make your job
> > easier Download IBM WebSphere Application Server v.1.0.1 based on
> > Apache Geronimo
> >
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=1216
> > 42 _______________________________________________
> > nant-developers mailing list
> > nant-developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nant-developers
> >
>
>



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Do you Yahoo!?
Next-gen email? Have it all with the all-new Yahoo! Mail Beta.
-------------------------------------------------------------------------
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-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to