I apologize in advance if I'm posting a question that has recently been answered. Many posts as oflate have gone many miles over my head...
Developersin my shoprecently got sick of reference problems and began using project references (while I was in a meeting Friday afternoon). This is good from
-Original Message-
I tend to agree with you. Corporate users don't really gel with the
opensource style 0.x release numbers. Lets table up a list
of things to
target at a 1.0 and see how that looks.
Right :) As I'm corporate developer as well, I mostly agree
with Sascha.
Any chance to make this task work for remote services?
In my build/deploy setup, I need to stop/start/restart services on our
production box, from our build box. I currently use the exec task
with netsvc.exe so that I can specify a remote machine. I think I got
netsvc.exe out of the Win2K
Hi Morris,
It should work with remote services, there's a machine (should I rename it
to server or computer ?) attribute that allows you to specifiy the
server name.
Gert
- Original Message -
From: Morris, Jason [EMAIL PROTECTED]
To: Nant-Developers (E-Mail) [EMAIL PROTECTED]
Sent:
At the moment obj files are compiled to a temp directory that gets removed
after a compile anyway. I am thinking maybe change to store obj files under
the obj/target directory just like vs.net, this way compilation can
potentially speed up as it doesn't have to recompiled unchanged files like
First, I think an ftp task would be great!
At the moment, I'm looking for a open source C# FTP client I can
liberally
copy and paste from.
I did a quick Google and came up with the following:
http://www.enterprisedt.com/downloads/csftp/csftp.html
I haven't had time to look at it but I
Yeah, I agree we should use an existing (open-source) library.
I'm pretty sure ftp will be available in some future revision of the .NET
Framework, but that will leave users of other frameworks in the cold, and we
wouldn't want that ...
Gert
- Original Message -
From: Clayton Harbour
There is patch to support very nice feature as it is described in docs:
FileSet. includes: comma-separated list of patterns of files that must
be included
Martin
fileset.patch
Description: Binary data
I don't like to use subdirectory of current path. Could be read only...
Maybe we could add some attribute to do build instead of rebuild?
Martin
- Original Message -
From: Eddie Tse [EMAIL PROTECTED]
To: 'Erick Thompson' [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Tuesday,
I found more spots where doc leaks:
1/ FileSet.
includes comma-separated list of patterns of files that must be
included; all files are included when omitted.
really? I want to use it and my hardly build comma-separated list throws:
Error creating file set. ---
Just my personal opinion, but I'm not sure I like this ...
It is just a personal preference, I do know Ant supports it (but I don't
think it's used much) ...
I prefer using multiple includes elements, that way it's easier to add xml
comments to each elements.
I would rather fix this in the docs
It is also possibility. I like this feature becouse it enables this:
-first build list of files somehow. e.g. by iterating by foreach and add it
to string
-use this string as input to fileset.
property name=docassemblies value=/
foreach item=File property=filename
in
12 matches
Mail list logo
