Cannot Check-In WCF Service References

[cjatk1]

Hi,
Sorry if this is a dumb question, but I am new to Vault.

I recently inherited a project which uses WCF Services. When we update the service definitions and refresh the Service References we are finding that we cannot check in all of the new References. This is a problem as there are multiple developers working on the same project and each time they do a "get latest" from Vault, they have to refresh these service references on their machines. Also, we are wanting to automate our build process with MSBuild (using the Vault command line), but as we need to manually update the References, this is presenting a roadblock.

I suspect that the issue has to do with the length of the reference path, for e.g.
D:\sourceCode\Current Projects\<Project Name>\<Project Version>\<Project>\<Project>.ServiceAccess\Service References\Library_Service3Reference\<Project>.ServiceAccess.Library_Service3Reference.LocationSessionItemTypeBalances.datasource I would like to shorten this path, but the company's policy is that all developers should structure their development directories in the above format.

Is there any way to increase the maximum allowed length that this path can be, so that Vault can check the updated references in?

Thank you in advance for your help.

[lbauer]

There's a limitation in the .NET framework. The .NET Framework cannot access a file with a path longer than 256 characters.

If you test checking in the references with a shorter path, does it work?