Does anyone know if there is a setting in Vault that will allow me to check out an ASP.NET page WITHOUT checking out its corresponding code behind? Right now, checking out one automatically checks out the other.
This really should be possible, as it is completely feasible to have one developer working on the presentation layer (ASP.NET page) which another is working on the logic (code-behind).
The only way I have been able to accomplish this so far is to manually edit the .cdproj file and remove the dependency of the ASP.NET page from the code-behind, but that is tedious for many many files, and there has got to be a better way.
Any help would be greatly appreciated.
Thanks!
-Steve
Checkout ASP.NET page WITHOUT checking out the code-behind
Moderator: SourceGear
Visual Studio will usually send Vault both files to be checked out. And, if fact, if it doesn't, we make sure we check out both anyway, because if you do end up modifying the second file later, but it isn't checked out, it causes problems on checkin.
Probably the best way to handle this is to turn off exclusive checkouts. That way if you haven't modified the file, there won't be a merge conflict, and even if you have modified it, Vault can try to automatically merge the two versions together.
Probably the best way to handle this is to turn off exclusive checkouts. That way if you haven't modified the file, there won't be a merge conflict, and even if you have modified it, Vault can try to automatically merge the two versions together.