> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Martin Aliger
> Sent: vrijdag 28 juli 2006 17:02
> To: 'Andrew Davey'; nant-developers@lists.sourceforge.net
> Subject: Re: [nant-dev] Continuing work on
>
&
rs@lists.sourceforge.net
> Subject: RE: [nant-dev] Continuing work on
>
> Mike wrote,
>
> > It would be a mistake to build any logic to parse VS2005 solution
> > files into NAnt because that file format is almost certainly going
> > away in the next version. (The only
does very good job on reference resolving. Just not good enough in
some
cases. There are even MS blogs about it, if you like to find them. It
do
_not_ follow project build order when building more projects at once.
It
could read order from .sln file, but thats all. It never try to find
out
corr
> I haven't had any problem resolving project dependencies.
> MSBuild seems to be smart enough to navigate the hintpaths
> defined in the various project files and deals with those
> just fine. Even the COM Interop stuff is working just peachy keen.
There are issues, believe me. Maybe its not
FWIW, I've had great success just using the task for
running MSBuild. It works just fine, and I can pass in any
of the parameters I want. We started using it just about 5
minutes after we started building our .NET 2.0 applications,
i.e. long enough to modify the build files to accomodate it.
> FWIW, I've had great success just using the task for
> running MSBuild. It works just fine, and I can pass in any
> of the parameters I want. We started using it just about 5
> minutes after we started building our .NET 2.0 applications,
> i.e. long enough to modify the build files to acco
Has anymore work been completed on the task?
However, developers who are in a similar position as myself, who have
relatively easy to compile solutions and are migrating their
applications
over to VS 2005, are forced to make a decision. Do we stick/use NAnt,
or
do we go with what Microsoft i
Hello,
>Has anymore work been completed on the task?
No, nothing serious since early january. I'm testing overall stability and
performance on our enterprise build. But most of our projects are still on
net-1.1. Anyway, it looks very well.
>Looking through the archives there was
Mike wrote,
> It would be a mistake to build any logic to parse VS2005 solution
> files into NAnt because that file format is almost certainly going
> away in the next version. (The only reason it's not an MSBuild file
> now is because MS basically didn't have time to finish it for VS2005).
I
Andy Davey wrote:
Has anymore work been completed on the task?
Nothing official that I know of, beyond what you've seen in
the archives. I tend to agree that, unless you make the
effort to dig back through this list's archives, NAnt looks
like it's basically dead in the water :( But word
Has anymore work been completed on the task?Looking through the archives there was mention of moving it into NAnt-Contrib, but the last time I looked that hasn't happened.I've downloaded the binaries and source that Martin posted in January, and they work ok (except for a bug in
FileUtil.CombineP
11 matches
Mail list logo
