None of that is even part of a typical Git workflow. Then it can help you do whatever revision-control voodoo you need to do when you want to edit a file. The main killer thing about SourceSafe's integration with Visual Studio is that you (and the editor) can tell at a glance which files you own, which must be checked out before you can edit, and which you cannot check out even if you want to. The second (which is related) is that when you are using the edit-merge workflow that both Subversion and Git encourage, you don't really need Visual Studio integration. There are a lot of hooks in it that are either way expensive to implement, or just flat out make no sense when you are using the more modern edit-merge workflow. The first is that the API pretty much assumes you are using a locked-checkout workflow. However, most folks don't bother with it for a couple of reasons. Visual Studio actually has a source control integration API to allow you to integrate third-party source control solutions into Visual Studio. I've looked into this a bit at work (both with Subversion and Git).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |