checkin policy question

i have a solution. with 3 project (p1,p2,p3)

now a developer1 modified and also add more file to p3

user developer1 add p4 to solution and reference p3.

developer1 compile and it work fine, but developeronly checkin p4 but not p3.

other dev get lastest and will fail. is there any kind of checkin policy to prevent this.

[376 byte] By [dealkk] at [2008-2-26]
# 1

You could write such a policy or through the use of some nature of continuous integration at least catch it just after check-in.

Take a look at the following thread and it's associated references.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=342812&SiteID=1

MichaelRuminer at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Version Control...

Visual Studio Team System

Site Classified