Page 1 of 1
How to exclude one file when awhole folder is added --> BUG?
Posted: Wed Sep 27, 2006 6:12 am
by binkle
Hi,
in my setup I add a complete folder (e.g. c:\\config\\*.*) to the msi.
But I'd like to exclude a single file (e.g. c:\\config\\base.cf) because Id like to add this extra to be able to check "Permanent file" and "never overwrite".
So I added "base.cf" to the exclude to the "*.*" entry of the folder added priviously.
But the base.cf is still copied when the folder is copied.
Is this a bug?
Greetings
Harry
Posted: Wed Sep 27, 2006 12:15 pm
by MichaelNesmith
I believe that should work. Be sure you used the correct notation for all fields in the command. Try to use a wildcard spec if it fails

Posted: Thu Sep 28, 2006 2:05 am
by binkle
Hi,
it definitely does not work.
Yes, if I but a * before "base.cf" (--> "*base.cf") it works, but then all files ending with ...base.cf are excluded.
You can try with a simple example:
- create a new default project
-add a complete folder (*.*) containing files named: base.cf, test.cf, testbase.cf
- put 'base.cf' in the exclude field and complile
Now can see in the compiler log window that the base.cf file is added.
If you change 'base.cf' to '*.base.cf' in the exclude field only the test.cf is added.
So there is a bug!
Posted: Thu Sep 28, 2006 7:25 am
by MichaelNesmith
I think that field is meant to accept wildcards only, sorry for the inconvenience. I'd try using a spec that matches only that file.
Posted: Thu Sep 28, 2006 8:30 am
by binkle
So it's not possible to exclude a single file....
You should fix this for further versions!!!
Posted: Thu Sep 28, 2006 1:50 pm
by MichaelNesmith
I think this field is not meant for single files, so this is by design. I can enter an item into the wishlist to exclude individual files, but usually wildcards are sufficient for most cases.
Posted: Fri Sep 29, 2006 4:07 am
by binkle
Yes, please do this.
Shouldn't be much effort to be implemented.
Thanks.