cloak a folder should mean cloak everything

[VaultUser6022]

I have Vault Standard 5.1.1 and I am using the enhanced client with Visual Studio 2008. I have a file system based Web Project in my solution. I am wanting Vault to ignore a folder and not track changes to the folder. I have marked the folder as Cloak using the Vault Client. What I am expecting to happen is by marking the folder as cloak the vault client would ignore all files and sub folders in that folder. This does not appear to be the case.

What appears to not happen is all sub folders are not cloaked. I had to manually cloak all sub folders. Next, if new folders are created under a cloaked folder it will not be ignored but Vault will attempt to commit the folder. The issue this causes is if these folders were temporary and at the time of commit they do not exist Vault will fail to commit because it cannot find the folder it wants to add and commit.

My only solution is to use the Vault client and undo these actions. This is error prone and because of the difficulty in working with the cloaked folder I have accidentally missed committing files. I may have accidentally undid actions to add newly added files to non-cloaked folders in the file system Web Site project.

[lbauer]

A cloak is a way to ignore folders in recursive operations, like Gets and Checkouts. For instance, if you're working on a project with 20 subfolders, and you just want the latest of subfolderA and subfolderE, you can cloak the rest of the subfolders so that you don't Get or Checkout more files than you need. Then you can Get Latest from the parent folder and only Get subfolders A and E.

If you invoke a command directly on a cloaked folder, that command is not ignored.
Cloaking doesn't prevent Adds or Deletes.

It sounds like what you'd like is an "Exclude from Source Control" function, which we do have logged as a feature request.