PDA

View Full Version : bug with copy files wildcards/filemasks


gribble
02-17-2005, 05:45 PM
I am copying files from a source directory tree (recursively) into a flat folder destination (copy all fies to root destination)

I have the Include mask set to:

*.exe
*.pdb


And the exclude mask is:

Setup.exe
txnlogsearch*.*
txlog.*
/obj
/External.NET
/Common.NET
AMS.Profile.pdb
WagonCommon.pdb



What i am noticing is that i have a built component called TxLogViewer.exe (and .pdb). These are being excluded from the copy step and i have found it is due to the exclusion TxLog.* (when i remove this line from the exclusion, the files copy OK).

The aim of this step is to copy all c++ built exe and pdb files (including TxLogViewer.exe) but i dont want to copy another .NET component which is called TxLog.exe


It seems that the exclusion TxLog.* is being treated like TxLog*.*


I have tested this on the latest 5.7 version and it is still happening



In my mind, the wildcards should work as they do in DOS.

i.e TxLogViewer should not cause a match on wildcard TxLog.* - only TxLog*.*


C:\wagering\wagon\main\code\TxLogViewer\Debug>dir TxLog.*
Volume in drive C has no label.
Volume Serial Number is 6847-7172

Directory of C:\wagering\wagon\main\code\TxLogViewer\Debug

File Not Found

C:\wagering\wagon\main\code\TxLogViewer\Debug>dir TxLog*.*
Volume in drive C has no label.
Volume Serial Number is 6847-7172

Directory of C:\wagering\wagon\main\code\TxLogViewer\Debug

17/02/2005 05:44 PM 3,510,350 TxLogViewer.exe
17/02/2005 05:44 PM 2,399,150 TxLogViewer.map
17/02/2005 05:38 PM 56,458 TxLogViewer.obj
17/02/2005 05:43 PM 3,560,096 TxLogViewer.pch
17/02/2005 05:44 PM 11,256,832 TxLogViewer.pdb
17/02/2005 05:36 PM 23,680 TxLogViewer.res
17/02/2005 05:38 PM 1,442,020 TxLogViewer.sbr
17/02/2005 05:38 PM 33,573 TxLogViewerDoc.obj
17/02/2005 05:38 PM 1,431,984 TxLogViewerDoc.sbr
9 File(s) 23,714,143 bytes
0 Dir(s) 6,082,904,064 bytes free

kinook
02-18-2005, 11:31 AM
That is in fact a bug (surprising that nobody ran into it until now). A workaround is to use

txlog.?*

gribble
02-18-2005, 07:55 PM
yeah it is surprising no-one came across it until now!

in the meantime, thanks for the work around :)