IDE/Vault integation fails to update *.VCP file

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

While redefining our eMVC++ IDE/Vault integration to refer to a relocated Vault repository folder, I have found that the integration process fails to update the *.VCP file for Microsoft's Emdedded Visual C++ IDE, while the *.VCW file is updated appropriately.

The reason for this change was that we renamed a folder in Vault and needed to reflect this path change within the IDE. After changing the assocation in the IDE, only the *.VCW file showed the new path, while the "Scc_ProjName" definition in the *.VCP file continued to refer to the old path. We had to update this file manually before checking in the *.VCW, *.VCP, and *.VCO files together as a single change set.

Here is the section of the *.VCP file that we had to change manually:

# Begin Project
# PROP AllowPerConfigDependencies 0
# PROP Scc_ProjName "$/Target Mobile Version 1 Branches/Target Mobile.1.43.2053.02/Target Mobile"
# PROP Scc_LocalPath "."
# PROP ATL_Project 2

Another reason for needing to change an existing IDE/Vault relationship would be when branching to create a new folder in Vault. IDE workspace files for the new folder would need to change to reflect the relationship with the new Vault repository folder.

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

Vault never modifies the content of a file (well, except for EOL settings and keyword expansion). Vault doesn't really have the knowledge required to know which lines of which files should change when a configuration change happens - the IDE is the place with this knowledge, and Visual Studio has some known problems when renaming/moving files.

Sorry to keep blaming VS...

Dave Schulte · Post by **Dave Schulte** » Mon Jan 17, 2005 10:11 am

Thanks Dan. Again, we'll just reflect this in our internal process notes. Are these things that you have (or can) report to Microsoft, or is this something that you would expect your customers to report?