How to: Cloak a Project
Visual SourceSafe allows you to use a "cloak" to designate a project that you generally do not work on, and for which you do not want to keep local copies. If you cloak a project, recursive Get, Check In, Check Out, Undo Check Out, and Show Difference (for projects) commands will not apply to that project. However, the direct commands with the cloaked project selected in Visual SourceSafe Explorer will apply to the project as usual.
When you cloak a project, its subprojects are implicitly cloaked when you use a recursive operation on the cloaked project or on a higher project in the project list.
To illustrate project cloaking, suppose that you work on a project called $/OurApp. This project has subprojects Code and Tests that you need, and another subproject Docs that you never use. You might find yourself recursively getting $/OurApp, and then deleting the Docs directory to obtain the configuration you need, but a better solution is to cloak $/OurApp/Docs. Even though the project is cloaked, you can still get this project or its files at any time. However, when you recursively get $/OurApp, Docs and all its subprojects will be ignored.
To cloak a Visual SourceSafe project:
In Visual SourceSafe Explorer, select the project to cloak.
On the File menu, click Properties.
Click the General tab if it is not already selected.
Select the This project is Cloaked for me check box.