RE: TFS and DBML Locking?
"SteveC" <stevec-dSSFwIkk4I/[email protected]>
| Newsgroups | gmane.comp.windows.off-topic |
|---|---|
| Message-ID | <872AD567FF27D94FBC3FB4F1CB9FCB3B0BEC78@cobalt.messaging.atomic9.net> |
My problem is that once someone branches, the exclusivity does not apply, so I can branch and work the DBML and you can also and when we merge back to trunk you will be allowed to overwrite my merge. So the exclusivity isn't "central" with that method. Hmmm... From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Rinaldi (TT) Sent: Wednesday, August 26, 2009 5:04 PM To: [email protected] Subject: RE: [OT] TFS and DBML Locking? Add the File Type to TFS by Right Clicking on your server in TFS and choosing Team Foundation Server Settings -> Source Control File Types. When you add the file type uncheck "Enable file merging and multiple check out". From: [email protected] [mailto:[email protected]] On Behalf Of SteveC Sent: Wednesday, August 26, 2009 3:21 PM To: [email protected] Subject: [OT] TFS and DBML Locking? If you're stuck with TFS (like me) and are stuck with LINQtoSQL (like me), how do you handle this situation where you need to exclusively lock the DBML so only 1 dev touches it at a time, but folks can branch and circumvent the lock? Thanks.