Add Files Question

[DanBlake]

We just started evaluating Valut for use on a large new project. Everything looks great so far.

I do have one thing I'm a little confused about.

If I have a working directory for $/ set to C:\WorkingSource and I right click on the $/ node in the client and select Add Files and then highlight C:\WorkingSource and press the add button, it adds the new files to $/WorkingSource. How do I get it to just recurively add any new files and directories to $/ like I want it to?

Thanks,
Dan

[jclausius]

Dan:

1) Highlight the folder you wish to be the "root" for the add. In you example, you were using $/
2) Invoke the "Add Files" dialog on that folder.
3) Within the Add Files/Folders, you can do add recursively by adding the parent folder for all objects. Select the parent folder in question on the left hand side of the dialog, and then click the "Add" button. In the bottom pane, you should now see a summary of the parent folder, as well as, sub folders and all the file entries, size, etc.

HTH

[DanBlake]

That is I think what I did, but it added it to $/WorkingSource not $/.

As an example I have a folder called C:\WorkingSource\Images.

So instead of getting the new files added to $/Images, the get added to $/WorkingSource/Images (even though the working director for $/ is set to C:\WorkingSource, and all of the folders under $/ are inheriting from it).

What am I missing/

Thanks,
Dan

[jclausius]

When adding files, the current working folder doesn't have too much bearing on the equation, except it will set the default folder in the Add Files / Folders dialog.

Try this:

1) Highlight the "owner folder". In your case, you wanted to create Images/ under $/. So highlight $/ in the tree view of the Vault client.
2) Invoke Add Files... with $/ still highlighted.
3) On the Add Files / Folders dialog, Highlight the C:\WorkingSource\Images\ on the left.
4) Click the Add Button. - Take note below. In the summary part, it should state $/Images/ will be created.
5) Click OK.
6) So now the Folder Images/ should be created under the parent folder $/.

[DanBlake]

My example was off a little in that I actually have another directory (Core Libs) before the image directory.

When I try to Add Files from C:\WorkingSource\CoreLibs\Image to $/CoreLibs/Image I get the following error.

[6/3/2004 9:09:43 PM] Item $/Core Libs/Image caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
[6/3/2004 9:09:43 PM] Transaction failed

[jclausius]

You cannot commit a recursive add if it will result in a name conflict with an existing item.

This is a guess, but in your case are you trying to add a directory images to $/CoreLibs/? If so, you will need to delete or rename the current $/CoreLibs/Images/ directory, as the add of Images/ is causing a name conflict.

[DanBlake]

Thanks for the explanantion, but not having this is a real pain. I want to be able to point at the root of a source tree on disk and have it add any new files and directories. This is something we do in Source Safe. Our directory strucutre is very fluid, and it is a pain to go through 50 directories to figure out what directories have been added, so that you remember to add them in the right way.

Is this something you are going to change in the future?

Dan

[jclausius]

I see. I didn't know the directory structure was already in place, and you wanted to add *only* the files that do not already exist in Vault.

I believe this enhancement has been suggested before. I'll add your name to the list.