Visual C++ integration question regarding working folders

Dave Schulte · Post by **Dave Schulte** » Tue Jan 18, 2005 2:39 pm

This is not an issue with Vault, but an issue with Microsoft Embedded Visual C++ (eMVC++).

We are having a problem with eMVC++ that you may have run into already and may know of a work-around.

eMVC++ seems to save SCC working folder information in the *.VCO file that it creates. This presents a problem when you have different developers working on the same project using different working folders. Within Vault, the working folder specifications are per developer, but there is only one .VCO file for a given project, which includes project specific settings that are not developer specific, like where to place a resulting executable or external library dependencies. Because of the developer-independent settings, we cannot simply start with a new .VCO file for each developer. We have checked int he *.VCW, *.VCP, AND *.VCO files into vault, since they contain information that we want tracked with each relase of our product.

It seems that because of the .VCO developer-specific settings, we cannot use IDE/Vault integration in a multi-developer environment. Have you run into this situation with either eMVC++ or Visual Studio? Have you found a way around this? For now, we are considering dropping use of IDE/Vault integration and just using the tools separately.

Thanks in advance for any insite you might provide.

dan · Post by **dan** » Tue Jan 18, 2005 4:13 pm

About the only way to handle this is to checkin the .vco file, but then have each developer modify it to reflect their own working folder, and then have them only check it in if it changes for a non-scc entry. Everyone will have Renegade/Needs Merge files hanging around, but there isn't much that can be done about that.

Ditching IDE integration is also a perfectly valid solution as well

Dave Schulte · Post by **Dave Schulte** » Tue Jan 18, 2005 5:17 pm

The problem is that once the working folder and SCC login are set in the .vco file, there doesn't seem to be a way to change them other than recreate the .vco file, which causes us to lose the developer-independent project settings that we have set in the first place (i.e., the ones we want all developers to use). Trying to use a .vco created by another developer results in a project file whose integration with Vault never works (because it finds that it (a) cannot connect to Vault using the given login and that (b) the working folder does not match that set in the given SCC tool.

Thanks for your reply.