On Fri, Mar 5, 2010 at 6:27 PM, David Kean wrote:
> Richard,
>
>
>
> Got a response. The fact that Directory.GetFiles returns the wrong file
> names is definitely a bug on our side and we’re now tracking it internally.
> Unfortunately, given we were are in the product cycle (ie a month away from
0. However, it will become a
candidate for a future release or service pack.
Regards
David
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of David Kean
Sent: Friday, March 05, 2010 9:39 AM
To: ozDotNet
Subject: RE: Problem with GetFiles() or me?
Thanks Ric
2010 5:52 AM
To: ozdotnet
Subject: Problem with GetFiles() or me?
Back to a programming topic...(rare for me).
I've knocked up a small console application to process a folder structure with
hundreds of thousands of small text files, read each file, strip off some
headers and append the resultin
Workaround: D:.
Adding the explicit current directory causes the returned strings to
be valid paths.
Do you want to add the bug to Connect?
--
Regards,
Mark Hurd, B.Sc.(Ma.)(Hons.)
(BTW Typos fixed below.)
On Sat, Mar 6, 2010 at 1:35 AM, Mark Hurd wrote:
> On Sat, Mar 6, 2010 at 12:21 AM, Ri
On Sat, Mar 6, 2010 at 12:21 AM, Richard Carde wrote:
>
> If I specify the path (first argument) as a drive letter (of a mapped drive)
> only, and that drive has a current working directory other than the root, it
> fails because GetFiles() returns an absolute path which is incorrect - it
> prepe
Back to a programming topic...(rare for me).
I've knocked up a small console application to process a folder structure
with hundreds of thousands of small text files, read each file, strip off
some headers and append the resulting data into a single large file. The
all worked fine until I needed
