[Mono-dev] We broke nant... again.

Marek Sieradzki marek.sieradzki at gmail.com
Thu Oct 19 14:13:17 EDT 2006

On 10/19/06, Leszek Ciesielski <skolima at gmail.com> wrote:
> Hi,
> on 14th of October a new nant version was released, fixing some bugs
> that were encountered when running on mono 1.1.17. On 16th mono 1.1.18
> was released, breaking nant - again. It is able to compile itself, but
> falls into an endless loop (seemingly in mono XML parser) when being
> run on more complex build files, with many 'include's and complex
> 'depends' attributes.

Just downgrade mono until nant is fixed.
> I am thinking (again) about dumping nant completely and switching to
> (ms/x)build. But as I tried to build a simple VS2005 project today I
> run into several problems.
> First: xbuild does not seem to support .sln files at all. This can be
> worked around by generating a .proj file from .sln in msbuid, or , for
> single-project solutions, using just the project file.
MS is autogenerating a .csproj file from .sln just before the build.
It's a simple target that uses MSBuild task. It can done the same way
in xbuild.

What you also need are working cross project references. It's still
not working in xbuild.
> Second: xbuild does not know the implicit targets defined in msbuild,
> like Rebuild or Clean (and probably others).
Someone should write them and test them.
> Third: xbuild does not work on windows. Well, it runs, but cannot
> compile anything. This is because to bug 79263 (
> http://bugzilla.ximian.com/show_bug.cgi?id=79263 ).
It won't change soon. Until it's fixed you can use msbuild.
> While first and third problems are not critical, the second one is...
> Anyone knows a solution (besides downgrading to mono 1.1.17) ?
Beside that my computer is temporarily broken (happening quite often
to me) xbuild needs more work in the core. MSBuild consists of:
framework + engine + common files + user projects. At the moment core
(Microsoft.Build.Engine) needs more NUnit tests.
When something goes wrong  (anywhere from the components list) new
users don't have patience to fix the bugs. Also I don't have a lot of
time recently.

More information about the Mono-devel-list mailing list