Personally, I agree with Karl... NAnt is just sooo much more powerful than plain old solutions...It's even worth maintaining NAnt and proj files - developers use csproj/vbproj files in VS, and building is done using 'clean' targets with wild-cards. It increases the developers overhead slightly, but
I'm not talking about spawning devenv, but moving the functionality ofthe task to a separate exe that would be runnable from NAnt
and essentially turning into a wrapper around the exe.I really don't see any significant advantage of creating a build file:then "nanting" this instead of running
Gary Feldman wrote:
> Jaroslaw Kowalski wrote:
>
>> Gary Feldman wrote:
>>
>>
>>> ...
>>> This would remove one of the major advantages that NAnt has over VS2003,
>>> namely it can build the
>>> solution much more rapidly than VS.
>>>
>>>
>> Can you elaborate on "rapidly"
Karl Palsson wrote:
> Speed is neither here nor there, as long as it's not t slow.
>
> Is speed really something you consider to be a major advantage of nant
> Gary?
>
Yes, at least for VS2003. Otherwise, what advantage does it have over
make/bash/python?
If it hadn't been for that speed
Jaroslaw Kowalski wrote:
> Gary Feldman wrote:
>
>> ...
>> This would remove one of the major advantages that NAnt has over VS2003,
>> namely it can build the
>> solution much more rapidly than VS.
>>
> Can you elaborate on "rapidly" ? I don't see any particular speed
> advantage here.
> > This would remove one of the major advantages that NAnt has over
> > VS2003, namely it can build the solution much more rapidly than VS.
> Can you elaborate on "rapidly" ? I don't see any particular
> speed advantage here.
I don't either, and it's certainly not one of the reasons I'm using
n
Gary Feldman wrote:
> Jaroslaw Kowalski wrote:
>
>> I never used the task. My personal opinion is that solution
>> building should be placed in a separate utility and NAnt should only
>> spawn it instead of implementing the entire build logic in-process.
>>
>>
> This would remove one
Jaroslaw Kowalski wrote:
> I never used the task. My personal opinion is that solution
> building should be placed in a separate utility and NAnt should only
> spawn it instead of implementing the entire build logic in-process.
>
This would remove one of the major advantages that NAnt has ov
Bonio Lopez wrote:
> Hi Jaroslaw,
> Why do you create a nant tasks "manually" instead of using solution task ?
> Is it because VS2005 not supported so far?
> Is somebody working to support VS2005 solution task?
> With best regards,
> Boni
>
I prefer "clean" tasks, because I prefer to specify so
On Behalf Of Jaroslaw
Kowalski
Sent: Montag, 17. Juli 2006 10:29
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] Synchronizing Visual Studio projects to NAnt build
Hi!
I often face the problem of synchronizing Visual Studio (both 2003 and
2005 versions) projects with NAnt. I usually
Hi!
I often face the problem of synchronizing Visual Studio (both 2003 and
2005 versions) projects with NAnt. I usually build with NAnt but want to
provide Visual Studio build files for my users. The problem is that I
tend to forget to update all the projects (*.csproj) with the newly
files or
11 matches
Mail list logo
