Thanks, Bill!
That
helps me quit a lot! - I'll try both ways.
Regards,
Tom
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Sent: Tuesday, 18 July
2006 12:20 AMTo: Thomas SchroedterCc:
nant-users@lists.sourceforge.netSubject: Re: [NAnt-users] MSI
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
Hi Tom,
There are two ways to do this. One is to use the
RemoveFile table, and the other is to use a custom action. The RemoveFile
table is probably simpler as it links to the conponents you are installing,
but unfortunately it's not directly supported by the task so
you have to use the elem
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
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
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf O
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
12 matches
Mail list logo
