Hi,
I encoutered a bug with the zip task (using NAnt 0.8.4). Some characters
(example: ç, é, è) are wrongly encoded in the zip file, which result in
invalid filenames, as reported when openning the file with winzip.
Nick
_
MSN
Hi,
I am planning on making some changes to the cvs task. We have been
working on a command line client for #cvslib that behaves the same as
the cvs and cvsnt command line clients. What I am going to do is use
this client to interface with the #cvslib component by executing the
cvs.exe
Seems like the flow scope should be called local in C#/programming
terms, and local would be private/container-only scoping. Having global be
the default is a good call, but only in come case, as you have identified in
if//foreach//etc.
I'm sure we will be able to say more with a patch; so we can
Hiya Jarek,
Yeah I wasn't sure about the nested if approach either, its easy enough
to change the behavior (I think). By default its Global anyway, and flow
fits the bill. Maybe Local should behave like Flow, and have one called
Private or something. Shrug :)
Come to think of it, there are very
Scott,
I'd really prefer to branch on this - it has the ability to really break
things. One of the first changes is changing the PropertyDictionary to
to store Property objects instead of string values. The property object
is where the accessibility level is stored.
While I am really keen to put
Hiya,
Yeah, I was considering the same thing. I also wondered whether this
could mean that there could be a unified type system. Filesets, string
properties etc.
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
