Conflict not handled by Visual Studio 2010 for dbproj files - by Vincent Labatut

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 836635 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/19/2014 3:44:34 AM
Access Restriction Public


We still have VS2010 database projects because later versions do not support code analysis extensibility,

we experience a problem when dbproj files are modified concurrently with TFS.

VS silently thinks it has the latest version and do not detect conflicts. it overwrites the server version resulting in project evolutions losses.

Workaround : get latest manually before changing the project.

Sign in to post a comment.
Posted by Microsoft on 3/19/2014 at 8:30 PM
The product team itself no longer directly accepting feedback for Microsoft Visual Studio 2010 and earlier products. You can get support for issues with Visual Studio 2010 and earlier by visiting one of the resources in the link below:
Posted by Microsoft on 3/19/2014 at 3:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If you require immediate assistance with this issue, please contact product support at
Posted by Vincent Labatut on 3/19/2014 at 3:45 AM
We can reproduce this behavior easily on all our dev machines

the problem does not occur for csproj files !