Add opt. not to set working folder during Vault/IDE integrat

Dave Schulte · Post by **Dave Schulte** » Sun Jan 16, 2005 6:16 pm

When integrating an IDE such as Microsoft's Embedded Visual C++, please add an option not to set a working folder association between the developer's local folder and the Vault repository folder that contains the IDE's workspace definintion files, if the Vault repository folder is already inheriting a working folder definition from some higher level repository folder.

This can potentially cause conflicts if a developer relocates their local workspace and forgets to update both the working folder assocaiton at the root repository folder and IDE repository folder levels. We are suggesting that our developers remove the IDE repository folder's working folder definition set by the Vault/IDE integration process to avoid such problems.

dan · Post by **dan** » Mon Jan 17, 2005 9:34 am

This is most probably something the IDE itself does rather than Vault. We set the working folder when Visual Studio tells us to. If there is a difference between what Vault does and some other SCC provider does, then it is possible that we can emulate different behavior, but generally we do what the IDE tells us, or it ends up causing more problems in different areas later.

Dave Schulte · Post by **Dave Schulte** » Mon Jan 17, 2005 9:42 am

Thanks Dan. For now, we will just tell folks to undo this working folder assocation, to avoid problems should a developer decide to relocate their root working folder in which the IDE folder resides.