monoman at gmail.com
Thu Nov 13 08:36:41 EST 2008
AFAIR, Monodevelop reads csprojs which are msbuild files but with specific
semantics, and deals with the needed tasks.
Monodevelop doesn't try to implement all msbuild functionality and specially
it's extensibility features, which are used by VS.NET.
It may be feasible to evolve Monodevelop to use xbuild but probably it would
impact the support for the other buildings tasks Monodevelop and its addins
currently support. The main reason is that msbuild (and therefore xbuild)
doesn't use Mono.Addins for its extensibility and doesn't consume/expose the
extension points in/to MD/MD-addins, but those of VS.NET/msbuild-addins.
Hope I didn't confuse things and this message can be of some help,
On Thu, Nov 13, 2008 at 7:54 AM, Andy Hume <andyhume32 at yahoo.co.uk> wrote:
> Michael Hutchinson wrote:
> > 2008/10/27 Jonathan Chambers <joncham at gmail.com>:
> >> Hello,
> >> I am looking to work on xbuild a bit, and so I started by looking
> >> at
> >> the the current tests and planned on writing some more.
> > Cool! I really think that xbuild is important, so I'm glad you're
> > looking at this.
> What confuses me is that we've got xbuild, which isn't very useful (I could
> never get it to compile a solution successfully), but Monodevelop uses .sln
> and .csproj files but _does_ work. So Monodevelop doesn't use xbuild?
> it have its own equivalent internally? Can't it be separated out and
> replace xbuild?
> View this message in context:
> Sent from the Mono - Dev mailing list archive at Nabble.com.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
Rafael "Monoman" Teixeira
"I myself am made entirely of flaws, stitched together with good
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list